Hi all,
After merging the akpm tree, today's linux-next build (arm64 allmodconfig)
failed like this:
./include/uapi/asm-generic/unistd.h:867:27: error: array index in initializer
exceeds array bounds
Caused by commit
390e5073c473 ("arch, mm: wire up memfd_secret system call where relevant")
Hi all,
After merging the akpm tree, today's linux-next build (x86_64
allmodconfig) failed like this:
mm/kasan/quarantine.c: In function 'quarantine_put':
mm/kasan/quarantine.c:198:3: error: 'return' with no value, in function
returning non-void [-Werror=return-type]
198 | return;
|
On Thu, Dec 3, 2020 at 9:52 AM Stephen Rothwell wrote:
>
> Hi all,
>
> After merging the akpm tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> mm/kasan/quarantine.c: In function 'quarantine_put':
> mm/kasan/quarantine.c:197:15: error: 'info' undeclared (first use in thi
Hi all,
After merging the akpm tree, today's linux-next build (x86_64
allmodconfig) failed like this:
mm/kasan/quarantine.c: In function 'quarantine_put':
mm/kasan/quarantine.c:197:15: error: 'info' undeclared (first use in this
function)
197 | qlink_free(&info->quarantine_link, cache);
Hi Mike,
On Sun, 15 Nov 2020 11:01:05 +0200 Mike Rapoport wrote:
>
> My preference would be to put the entire function body in '#ifdef
> CONFIG_MEMCG' here.
OK, so today I used this:
From: Stephen Rothwell
Date: Mon, 16 Nov 2020 16:55:10 +1100
Subject: [PATCH] secretmem-add-memcg-accounting-fi
On Fri, Nov 13, 2020 at 05:14:52PM -0800, Andrew Morton wrote:
> On Fri, 13 Nov 2020 18:02:39 +1100 Stephen Rothwell
> wrote:
>
> > Hi all,
> >
> > After merging the akpm tree, today's linux-next build (i386 defconfig)
> > failed like this:
> >
> > mm/secretmem.c: In function 'secretmem_memcg_
On Fri, 13 Nov 2020 18:02:39 +1100 Stephen Rothwell
wrote:
> Hi all,
>
> After merging the akpm tree, today's linux-next build (i386 defconfig)
> failed like this:
>
> mm/secretmem.c: In function 'secretmem_memcg_charge':
> mm/secretmem.c:72:4: error: 'struct page' has no member named 'memcg_d
Hi all,
After merging the akpm tree, today's linux-next build (i386 defconfig)
failed like this:
mm/secretmem.c: In function 'secretmem_memcg_charge':
mm/secretmem.c:72:4: error: 'struct page' has no member named 'memcg_data'
72 | p->memcg_data = page->memcg_data;
|^~
mm/secretmem.
Hi all,
After merging the akpm tree, today's linux-next build (x86_64
allmodconfig) failed like this:
mm/kasan/shadow.c: In function 'kasan_poison_memory':
mm/kasan/shadow.c:88:6: error: implicit declaration of function
'is_kfence_address' [-Werror=implicit-function-declaration]
88 | if (is_
Thanks,
the fix looks correct.
Hi all,
After merging the akpm tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
mm/madvise.c: In function '__do_sys_process_madvise':
mm/madvise.c:1194:9: error: implicit declaration of function
'compat_import_iovec'; did you mean 'import_iovec'?
[-Werror=implicit-func
Hi all,
After merging the akpm tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
mm/madvise.c: In function 'madv_import_iovec':
mm/madvise.c:1233:6: error: implicit declaration of function
'in_compat_syscall' [-Werror=implicit-function-declaration]
1233 | if (in_compat
Hi all,
On Thu, 4 Jun 2020 16:44:42 +1000 Stephen Rothwell
wrote:
>
> Hi all,
>
> After merging the akpm tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> arch/powerpc/mm/ptdump/ptdump.c: In function 'walk_pagetables':
> arch/powerpc/mm/ptdump/ptdump.c:337:25: error
Hi all,
After merging the akpm tree, today's linux-next build (powerpc
allyesconfig) failed like this:
arch/powerpc/mm/ptdump/ptdump.c: In function 'walk_pagetables':
arch/powerpc/mm/ptdump/ptdump.c:337:25: error: implicit declaration of function
'pgd_is_leaf'; did you mean 'p4d_is_leaf'?
[-Wer
On Tue, 2 Jun 2020 19:57:41 +1000 Stephen Rothwell
wrote:
> Subject: [PATCH] turns out that probe_user_write is used in modular code
>
> Signed-off-by: Stephen Rothwell
> ---
> mm/maccess.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/mm/maccess.c b/mm/maccess.c
> index ddfda8e6f
Hi all,
After merging the akpm tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
ERROR: modpost: ".probe_user_write" [arch/powerpc/kvm/kvm-hv.ko] undefined!
Caused by patch
"maccess: unexport probe_kernel_write and probe_user_write"
"These two functions are not used
This looks correct, thanks.
Hi all,
After merging the akpm tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_process.c: In function
'kfd_sdma_activity_worker':
drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_process.c:117:2: error: implicit
declaration of function 'us
Hi John,
On Mon, 25 May 2020 11:18:46 -0700 John Hubbard wrote:
>
> Yes, looks good. And in fact, Andrew has the same fix-up in the mmotm branch
> of
> linux-next.git, as
>
> commit a76c281a8ddd
> ("mmap-locking-api-rename-mmap_sem-to-mmap_lock-fix").
For some reason that was not include
On 2020-05-25 05:17, Stephen Rothwell wrote:
Hi all,
After merging the akpm tree, today's linux-next build (x86_64
allmodconfig) failed like this:
In file included from include/linux/kernel.h:14,
from mm/gup.c:2:
mm/gup.c: In function 'internal_get_user_pages_fast':
mm/gup.c:2
Hi all,
After merging the akpm tree, today's linux-next build (x86_64
allmodconfig) failed like this:
In file included from include/linux/kernel.h:14,
from mm/gup.c:2:
mm/gup.c: In function 'internal_get_user_pages_fast':
mm/gup.c:2732:33: error: 'struct mm_struct' has no member
On Tue, Feb 26, 2019 at 06:39:15PM +1100, Stephen Rothwell wrote:
> Hi Andrew,
>
> After merging the akpm tree, today's linux-next build (powerpc
> allnoconfig) failed like this:
>
> /home/sfr/next/next/arch/powerpc/kernel/setup_32.c:176:21: error:
> redefinition of 'alloc_stack'
> static void
Hi Andrew,
After merging the akpm tree, today's linux-next build (powerpc
allnoconfig) failed like this:
/home/sfr/next/next/arch/powerpc/kernel/setup_32.c:176:21: error: redefinition
of 'alloc_stack'
static void *__init alloc_stack(void)
^~~
/home/sfr/next/next/arc
Hi Anshuman,
On Wed, 12 Dec 2018 22:35:38 +0530 Anshuman Khandual
wrote:
>
> On 12/03/2018 12:30 PM, Stephen Rothwell wrote:
> > Hi Andrew,
> >
> > After merging the akpm tree, today's linux-next build (powerpc_le perf)
> > failed like this:
> >
> > bench/numa.c:37:10: fatal error: linux/numa.
On 12/03/2018 12:30 PM, Stephen Rothwell wrote:
> Hi Andrew,
>
> After merging the akpm tree, today's linux-next build (powerpc_le perf)
> failed like this:
>
> bench/numa.c:37:10: fatal error: linux/numa.h: No such file or directory
> #include
> ^~
>
> Caused by patch
On 12/03/2018 12:30 PM, Stephen Rothwell wrote:
> Hi Andrew,
>
> After merging the akpm tree, today's linux-next build (powerpc_le perf)
> failed like this:
>
> bench/numa.c:37:10: fatal error: linux/numa.h: No such file or directory
> #include
> ^~
>
> Caused by patch
Hi Andrew,
After merging the akpm tree, today's linux-next build (powerpc_le perf)
failed like this:
bench/numa.c:37:10: fatal error: linux/numa.h: No such file or directory
#include
^~
Caused by patches
"mm: replace all open encodings for NUMA_NO_NODE"
"mm-replace-a
On 11/30/2018 11:00 AM, Stephen Rothwell wrote:
> Hi Andrew,
>
> After merging the akpm tree, today's linux-next build (powerpc_le perf)
> failed like this:
>
> bench/numa.c: In function 'bind_to_node':
> bench/numa.c:301:21: error: 'NUMA_NO_NODE' undeclared (first use in this
> function); di
Hi Andrew,
After merging the akpm tree, today's linux-next build (powerpc_le perf)
failed like this:
bench/numa.c: In function 'bind_to_node':
bench/numa.c:301:21: error: 'NUMA_NO_NODE' undeclared (first use in this
function); did you mean 'NUMA_NUM_NODES'?
if (target_node == NUMA_NO_NODE) {
* Stephen Rothwell wrote:
> Hi all,
>
> On Mon, 8 Oct 2018 19:03:41 +1100 Stephen Rothwell
> wrote:
> >
> > After merging the akpm tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > arch/x86/mm/kaslr.c:26:10: fatal error: linux/bootmem.h: No such file or
> >
Hi all,
On Mon, 8 Oct 2018 19:03:41 +1100 Stephen Rothwell
wrote:
>
> After merging the akpm tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> arch/x86/mm/kaslr.c:26:10: fatal error: linux/bootmem.h: No such file or
> directory
> #include
> ^~
Hi all,
After merging the akpm tree, today's linux-next build (x86_64
allmodconfig) failed like this:
arch/x86/mm/kaslr.c:26:10: fatal error: linux/bootmem.h: No such file or
directory
#include
^
Caused by patch
"mm: remove include/linux/bootmem.h"
interacting wi
Hi all,
After merging the akpm tree, today's linux-next build (x86_64 allnoconfig)
failed like this:
Caused by commit
a20bb0583751 ("dma-direct: add an explicit dma_direct_get_required_mask")
from the dma-mappgin tree conflicting with patch
"mm: remove include/linux/bootmem.h"
I have app
Hi Greg,
On Wed, 21 Mar 2018 11:02:08 +0100 Greg Kroah-Hartman
wrote:
>
> Patch is now queued up, thanks.
Excellent.
--
Cheers,
Stephen Rothwell
pgpMuNJUwYuTO.pgp
Description: OpenPGP digital signature
On Wed, Mar 21, 2018 at 07:17:27PM +1100, Stephen Rothwell wrote:
> Hi Andrew,
>
> After merging the akpm tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> drivers/base/firmware_loader/fallback.c: In function 'map_fw_priv_pages':
> drivers/base/firmware_loader/fallback
Hi Andrew,
After merging the akpm tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/base/firmware_loader/fallback.c: In function 'map_fw_priv_pages':
drivers/base/firmware_loader/fallback.c:232:2: error: implicit declaration of
function 'vunmap'; did you mean 'kunma
Hi Andrew,
After merging the akpm tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
lib/cpumask.c: In function 'cpumask_next_and':
lib/cpumask.c:39:9: error: implicit declaration of function 'find_next_and_bit'
[-Werror=implicit-function-declaration]
return find_ne
On Tue, Aug 1, 2017 at 8:40 PM, Kees Cook wrote:
>>
>> I don't know why this has turned up now. I have just left it broken
>> for now and would appreciate any fix.
>
> Thanks for the heads-up! I'm not sure why this suddenly appeared
> either, but Arnd has sent a patch for this now.
The main diff
On Mon, Jul 31, 2017 at 11:25 PM, Stephen Rothwell
wrote:
> Hi Andrew,
>
> After merging the akpm tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> In file included from arch/powerpc/include/asm/paca.h:19:0,
> from arch/powerpc/include/asm/hw_irq.h:42,
Hi Andrew,
After merging the akpm tree, today's linux-next build (powerpc
allyesconfig) failed like this:
In file included from arch/powerpc/include/asm/paca.h:19:0,
from arch/powerpc/include/asm/hw_irq.h:42,
from arch/powerpc/include/asm/irqflags.h:11,
From: Stephen Rothwell
Date: Fri, 30 Jun 2017 16:32:41 +1000
> From: Stephen Rothwell
> Date: Fri, 30 Jun 2017 16:24:35 +1000
> Subject: [PATCH] net/mlx5: fix memcpy limit?
>
> Signed-off-by: Stephen Rothwell
Applied, thanks.
Hi all,
On Fri, 30 Jun 2017 16:32:41 +1000 Stephen Rothwell
wrote:
>
> After merging the akpm tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> In file included from include/linux/bitmap.h:8:0,
> from include/linux/cpumask.h:11,
> fro
Hi all,
After merging the akpm tree, today's linux-next build (x86_64
allmodconfig) failed like this:
In file included from include/linux/bitmap.h:8:0,
from include/linux/cpumask.h:11,
from include/linux/mm_types_task.h:13,
from include/linux/mm_
Hi Michal,
On Mon, 26 Jun 2017 09:13:46 +0200 Michal Hocko wrote:
>
> On Mon 26-06-17 16:53:43, Stephen Rothwell wrote:
> >
> > After merging the akpm tree, today's linux-next build (sparc64 defconfig)
> > failed like this:
> >
> > arch/sparc/kernel/mdesc.c: In function 'mdesc_kmalloc':
> > arc
On Mon 26-06-17 16:53:43, Stephen Rothwell wrote:
> Hi Andrew,
>
> After merging the akpm tree, today's linux-next build (sparc64 defconfig)
> failed like this:
>
> arch/sparc/kernel/mdesc.c: In function 'mdesc_kmalloc':
> arch/sparc/kernel/mdesc.c:208:48: error: '__GFP_REPEAT' undeclared (first
Hi Andrew,
After merging the akpm tree, today's linux-next build (sparc64 defconfig)
failed like this:
arch/sparc/kernel/mdesc.c: In function 'mdesc_kmalloc':
arch/sparc/kernel/mdesc.c:208:48: error: '__GFP_REPEAT' undeclared (first use
in this function)
base = kmalloc(handle_size + 15, GFP_KE
Hi all,
After merging the akpm tree, today's linux-next build (x86_64
allmodconfig) failed like this:
fs/gfs2/bmap.c: In function 'sweep_bh_for_rgrps':
fs/gfs2/bmap.c:1075:5: error: 'CURRENT_TIME' undeclared (first use in this
function)
CURRENT_TIME;
^
fs/gfs2/bmap.c:1075:5: note: each
Hi all,
After merging the akpm tree, today's linux-next build (x86_64
allmodconfig) failed like this:
arch/x86/kernel/kprobes/opt.c: In function 'arch_prepare_optimized_kprobe':
arch/x86/kernel/kprobes/opt.c:357:2: error: implicit declaration of function
'set_memory_rw' [-Werror=implicit-functio
Hi Andrew,
After merging the akpm tree, today's linux-next build (x86_64
allmodconfig) failed like this:
mm/migrate.c: In function 'migrate_vma_insert_page':
mm/migrate.c:2491:23: error: passing argument 2 of 'pud_alloc' from
incompatible pointer type [-Werror=incompatible-pointer-types]
pudp
On Mon 20-03-17 16:37:35, Stephen Rothwell wrote:
> Hi Andrew,
>
> After merging the akpm tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> fs/f2fs/node.c: In function 'init_free_nid_cache':
> fs/f2fs/node.c:2634:25: error: implicit declaration of function
> 'f2fs_kvza
On 03/20, Michal Hocko wrote:
> On Mon 20-03-17 16:37:35, Stephen Rothwell wrote:
> > Hi Andrew,
> >
> > After merging the akpm tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > fs/f2fs/node.c: In function 'init_free_nid_cache':
> > fs/f2fs/node.c:2634:25: error:
Hi Andrew,
After merging the akpm tree, today's linux-next build (x86_64
allmodconfig) failed like this:
fs/f2fs/node.c: In function 'init_free_nid_cache':
fs/f2fs/node.c:2634:25: error: implicit declaration of function 'f2fs_kvzalloc'
[-Werror=implicit-function-declaration]
nm_i->free_nid_cou
On 03/06/2017 07:07 PM, Stephen Rothwell wrote:
> Hi Andrew,
>
> After merging the akpm tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> In file included from include/net/sock.h:64:0,
> from include/linux/tcp.h:23,
> from include/l
Hi Andrew,
After merging the akpm tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
In file included from include/net/sock.h:64:0,
from include/linux/tcp.h:23,
from include/linux/ipv6.h:83,
from include/net/ipv6.h:16,
Hi Andrew,
After merging the akpm tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
arch/arm/kernel/machine_kexec.c: In function 'machine_kexec':
arch/arm/kernel/machine_kexec.c:163:2: error: implicit declaration of function
'set_kernel_text_rw' [-Werror=implicit-function
Hi Andrew,
After merging the akpm tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
lib/radix-tree.c: In function 'radix_tree_iter_delete':
lib/radix-tree.c:1952:3: error: too few arguments to function
'__radix_tree_delete_node'
__radix_tree_delete_node(root, node);
On Tue, 26 Jan 2016 21:51:30 +0100,
Stephen Rothwell wrote:
>
> Hi Takashi,
>
> On Mon, 25 Jan 2016 14:45:55 +0100 Takashi Iwai wrote:
> >
> > From: Takashi Iwai
> > Subject: [PATCH v2] ALSA: compress: Disable GET_CODEC_CAPS ioctl for some
> > architectures
> >
> > Some architectures like Pow
Hi Takashi,
On Mon, 25 Jan 2016 14:45:55 +0100 Takashi Iwai wrote:
>
> From: Takashi Iwai
> Subject: [PATCH v2] ALSA: compress: Disable GET_CODEC_CAPS ioctl for some
> architectures
>
> Some architectures like PowerPC can handle the maximum struct size in
> an ioctl only up to 13 bits, and str
On Mon, Jan 25, 2016 at 01:55:46PM +, Mark Brown wrote:
>
> though we will need to come up with an alternative solution for the
> affected architectures if anyone ends up caring (MIPS or PowerPC might
> possibly).
Okay I did some rethink on this. So we should be able to make
MAX_NUM_CODEC_DES
On Mon, Jan 25, 2016 at 02:45:55PM +0100, Takashi Iwai wrote:
> Below is the revised one.
Acked-by: Vinod Koul
Thanks for fixing this up...
--
~Vinod
On Mon, Jan 25, 2016 at 02:45:55PM +0100, Takashi Iwai wrote:
> On Mon, 25 Jan 2016 14:10:37 +0100,
> Takashi Iwai wrote:
> >
> > On Mon, 25 Jan 2016 12:41:50 +0100,
> > Mark Brown wrote:
> > >
> >
> > Signed-off-by: Takashi Iwai
> > ---
> > sound/core/compress_offload.c | 11 +++
> >
On Mon, Jan 25, 2016 at 02:45:55PM +0100, Takashi Iwai wrote:
> Argh, a typo here. I forgot to refresh the patch, sorry.
> Below is the revised one.
This makes sense to me.
Reviwed-by: Mark Brown
though we will need to come up with an alternative solution for the
affected architectures if an
On Mon, 25 Jan 2016 14:10:37 +0100,
Takashi Iwai wrote:
>
> On Mon, 25 Jan 2016 12:41:50 +0100,
> Mark Brown wrote:
> >
> > On Mon, Jan 25, 2016 at 10:29:54AM +0100, Takashi Iwai wrote:
> > > Stephen Rothwell wrote:
> >
> > > > diff --git a/sound/soc/codecs/Kconfig b/sound/soc/codecs/Kconfig
> >
On Mon, 25 Jan 2016 12:41:50 +0100,
Mark Brown wrote:
>
> On Mon, Jan 25, 2016 at 10:29:54AM +0100, Takashi Iwai wrote:
> > Stephen Rothwell wrote:
>
> > > diff --git a/sound/soc/codecs/Kconfig b/sound/soc/codecs/Kconfig
> > > index 50693c867e71..ee5f36b9c787 100644
> > > --- a/sound/soc/codecs/K
On Mon, Jan 25, 2016 at 10:29:54AM +0100, Takashi Iwai wrote:
> Stephen Rothwell wrote:
> > diff --git a/sound/soc/codecs/Kconfig b/sound/soc/codecs/Kconfig
> > index 50693c867e71..ee5f36b9c787 100644
> > --- a/sound/soc/codecs/Kconfig
> > +++ b/sound/soc/codecs/Kconfig
> > @@ -13,6 +13,7 @@ menu
On Mon, Jan 25, 2016 at 12:03:54PM +0100, Takashi Iwai wrote:
> On Mon, 25 Jan 2016 11:45:56 +0100,
> Sudip Mukherjee wrote:
> >
> > On Mon, Jan 25, 2016 at 10:29:54AM +0100, Takashi Iwai wrote:
> > > On Fri, 22 Jan 2016 03:40:45 +0100,
> > > Stephen Rothwell wrote:
> > > >
> > > > Hi all,
> > >
On Mon, 25 Jan 2016 11:45:56 +0100,
Sudip Mukherjee wrote:
>
> On Mon, Jan 25, 2016 at 10:29:54AM +0100, Takashi Iwai wrote:
> > On Fri, 22 Jan 2016 03:40:45 +0100,
> > Stephen Rothwell wrote:
> > >
> > > Hi all,
> > >
> > > On Fri, 22 Jan 2016 11:24:42 +1100 Stephen Rothwell
> > > wrote:
> >
On Mon, Jan 25, 2016 at 10:29:54AM +0100, Takashi Iwai wrote:
> On Fri, 22 Jan 2016 03:40:45 +0100,
> Stephen Rothwell wrote:
> >
> > Hi all,
> >
> > On Fri, 22 Jan 2016 11:24:42 +1100 Stephen Rothwell
> > wrote:
> > >
> > > On Thu, 21 Jan 2016 07:38:59 +1100 Stephen Rothwell
> > > wrote:
> >
On Mon, 25 Jan 2016 11:41:12 +0100,
Vinod Koul wrote:
>
> On Mon, Jan 25, 2016 at 10:29:54AM +0100, Takashi Iwai wrote:
> > On Fri, 22 Jan 2016 03:40:45 +0100,
> > Stephen Rothwell wrote:
> > >
> > > Hi all,
> > >
> > > On Fri, 22 Jan 2016 11:24:42 +1100 Stephen Rothwell
> > > wrote:
> > > >
>
On Mon, Jan 25, 2016 at 10:29:54AM +0100, Takashi Iwai wrote:
> On Fri, 22 Jan 2016 03:40:45 +0100,
> Stephen Rothwell wrote:
> >
> > Hi all,
> >
> > On Fri, 22 Jan 2016 11:24:42 +1100 Stephen Rothwell
> > wrote:
> > >
> > > On Thu, 21 Jan 2016 07:38:59 +1100 Stephen Rothwell
> > > wrote:
> >
On Mon, 25 Jan 2016 10:40:14 +0100,
Michael Ellerman wrote:
>
> On Mon, 2016-01-25 at 10:29 +0100, Takashi Iwai wrote:
> > On Fri, 22 Jan 2016 03:40:45 +0100, Stephen Rothwell wrote:
> > > diff --git a/sound/soc/codecs/Kconfig b/sound/soc/codecs/Kconfig
> > > index 50693c867e71..ee5f36b9c787 10064
On Mon, 2016-01-25 at 10:29 +0100, Takashi Iwai wrote:
> On Fri, 22 Jan 2016 03:40:45 +0100, Stephen Rothwell wrote:
> > diff --git a/sound/soc/codecs/Kconfig b/sound/soc/codecs/Kconfig
> > index 50693c867e71..ee5f36b9c787 100644
> > --- a/sound/soc/codecs/Kconfig
> > +++ b/sound/soc/codecs/Kconfig
On Fri, 22 Jan 2016 03:40:45 +0100,
Stephen Rothwell wrote:
>
> Hi all,
>
> On Fri, 22 Jan 2016 11:24:42 +1100 Stephen Rothwell
> wrote:
> >
> > On Thu, 21 Jan 2016 07:38:59 +1100 Stephen Rothwell
> > wrote:
> > >
> > > On Wed, 20 Jan 2016 15:09:47 +0100 Takashi Iwai wrote:
> > > >
> > > >
Hi all,
On Fri, 22 Jan 2016 11:24:42 +1100 Stephen Rothwell
wrote:
>
> On Thu, 21 Jan 2016 07:38:59 +1100 Stephen Rothwell
> wrote:
> >
> > On Wed, 20 Jan 2016 15:09:47 +0100 Takashi Iwai wrote:
> > >
> > > On Sat, 16 Jan 2016 09:51:29 +0100,
> > > Takashi Iwai wrote:
> > > >
> > > > T
Hi all,
On Fri, 22 Jan 2016 11:24:42 +1100 Stephen Rothwell
wrote:
>
> On Thu, 21 Jan 2016 07:38:59 +1100 Stephen Rothwell
> wrote:
> >
> > On Wed, 20 Jan 2016 15:09:47 +0100 Takashi Iwai wrote:
> > >
> > > On Sat, 16 Jan 2016 09:51:29 +0100,
> > > Takashi Iwai wrote:
> > > >
> > > > T
Hi all,
On Thu, 21 Jan 2016 07:38:59 +1100 Stephen Rothwell
wrote:
>
> On Wed, 20 Jan 2016 15:09:47 +0100 Takashi Iwai wrote:
> >
> > On Sat, 16 Jan 2016 09:51:29 +0100,
> > Takashi Iwai wrote:
> > >
> > > There are a few ways to fix this, but all are not comfortable.
> > >
> > > A. Disable
Hi Takashi,
On Wed, 20 Jan 2016 15:09:47 +0100 Takashi Iwai wrote:
>
> On Sat, 16 Jan 2016 09:51:29 +0100,
> Takashi Iwai wrote:
> >
> > There are a few ways to fix this, but all are not comfortable.
> >
> > A. Disable compress API for powerpc.
This also affects alpha, mips and (maybe) sparc.
Hi Andrew,
After merging the akpm tree, today's linux-next build (powerpc
allyesconfig) failed like this:
sound/core/compress_offload.c: In function 'snd_compr_ioctl':
/home/sfr/next/next/sound/core/compress_offload.c:804:2: error: case label does
not reduce to an integer constant
case _IOC_NR
Hi Andrew,
After merging the akpm tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
fs/ext4/mballoc.c: In function 'ext4_mb_check_group_pa':
/home/sfr/next/next/fs/ext4/mballoc.c:3335:17: error: implicit declaration of
function 'abs64' [-Werror=implicit-function-declarati
Hi Andrew,
After merging the akpm tree, today's linux-next build (x86_64
allmodconfig) failed like this:
kernel/time/clocksource.c: In function 'clocksource_watchdog':
kernel/time/clocksource.c:220:3: error: implicit declaration of function
'abs64' [-Werror=implicit-function-declaration]
if (
Hi Andrew,
After merging the akpm tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/net/ieee802154/at86rf230.c: In function 'at86rf230_stats_show':
drivers/net/ieee802154/at86rf230.c:1650:6: error: void value not ignored as it
ought to be
ret = seq_printf(file, "SU
Hi Andrew,
After merging the akpm tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
fs/nsfs.c: In function 'nsfs_show_path':
fs/nsfs.c:145:2: error: void value not ignored as it ought to be
return seq_printf(seq, "%s:[%lu]", ns_ops->name, inode->i_ino);
^
fs/nsfs.c:146
Hi Andrew,
After merging the akpm tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
fs/nsfs.c: In function 'nsfs_show_path':
fs/nsfs.c:145:2: error: void value not ignored as it ought to be
return seq_printf(seq, "%s:[%lu]", ns_ops->name, inode->i_ino);
^
fs/nsfs.c:146
Hi Andrew,
After merging the akpm tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/crypto/marvell/cesa.c: In function 'mv_cesa_get_sram':
drivers/crypto/marvell/cesa.c:324:2: error: implicit declaration of function
'of_get_named_gen_pool' [-Werror=implicit-function-
Hi Thierry,
On Thu, 6 Nov 2014 12:24:00 +0100 Thierry Reding
wrote:
>
> I fixed this using the attached patch.
I will apply this to linux-next today (unless Andrew beats me to it).
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
pgptxz_cahjEZ.pgp
Description: OpenPGP di
On Thu, Nov 06, 2014 at 12:24:00PM +0100, Thierry Reding wrote:
> On Thu, Nov 06, 2014 at 07:36:18PM +1100, Stephen Rothwell wrote:
> > Hi Andrew,
> >
> > After merging the akpm tree, today's linux-next build (sparc defconfig)
> > failed like this:
> >
> > mm/slab.c: In function 'slab_alloc':
> >
On Thu, Nov 06, 2014 at 07:36:18PM +1100, Stephen Rothwell wrote:
> Hi Andrew,
>
> After merging the akpm tree, today's linux-next build (sparc defconfig)
> failed like this:
>
> mm/slab.c: In function 'slab_alloc':
> mm/slab.c:3260:4: error: implicit declaration of function 'slab_free'
> [-Werr
Hi Andrew,
After merging the akpm tree, today's linux-next build (sparc defconfig)
failed like this:
mm/slab.c: In function 'slab_alloc':
mm/slab.c:3260:4: error: implicit declaration of function 'slab_free'
[-Werror=implicit-function-declaration]
slab_free(cachep, objp);
^
mm/slab.c: At
Hi Don,
On Tue, 26 Aug 2014 09:54:17 -0400 Don Zickus wrote:
>
> On Tue, Aug 26, 2014 at 05:18:18PM +1000, Stephen Rothwell wrote:
> > Hi Andrew,
> >
> > After merging the akpm tree, today's linux-next build (sparc64
> > defconfig) failed like this:
> >
> > kernel/built-in.o: In function `proc_
On Tue, Aug 26, 2014 at 05:18:18PM +1000, Stephen Rothwell wrote:
> Hi Andrew,
>
> After merging the akpm tree, today's linux-next build (sparc64
> defconfig) failed like this:
>
> kernel/built-in.o: In function `proc_dowatchdog':
> (.text+0x6a620): undefined reference to
> `watchdog_hardlockup_
Hi Andrew,
After merging the akpm tree, today's linux-next build (sparc64
defconfig) failed like this:
kernel/built-in.o: In function `proc_dowatchdog':
(.text+0x6a620): undefined reference to
`watchdog_hardlockup_detector_is_enabled'
kernel/built-in.o: In function `proc_dowatchdog':
(.text+0x6a
On Wed 16-07-14 18:26:41, Stephen Rothwell wrote:
> Hi Andrew,
>
> After merging the akpm tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> mm/memcontrol.c:5269:12: error: 'CFTYPE_INSANE' undeclared here (not in a
> function)
>.flags = CFTYPE_INSANE,
>
Hi Andrew,
After merging the akpm tree, today's linux-next build (x86_64
allmodconfig) failed like this:
mm/memcontrol.c:5269:12: error: 'CFTYPE_INSANE' undeclared here (not in a
function)
.flags = CFTYPE_INSANE,
^
Caused by commit 8fa6a8baeffc ("memcg: deprecate memory.force_emp
On Fri, 7 Mar 2014 11:05:49 -0600 (CST) Christoph Lameter
wrote:
> On Thu, 6 Mar 2014, Andrew Morton wrote:
>
> > > So, by "the whole series" do you mean just/all these:
> > >
> > > percpu-add-raw_cpu_ops.patch
> > > ...
> > > sh-replace-__get_cpu_var-uses.patch
> >
> > Yep. Commented out in h
On Thu, 6 Mar 2014, Andrew Morton wrote:
> > So, by "the whole series" do you mean just/all these:
> >
> > percpu-add-raw_cpu_ops.patch
> > ...
> > sh-replace-__get_cpu_var-uses.patch
>
> Yep. Commented out in http://ozlabs.org/~akpm/mmots/series
>
> > If so, I will remove them from my tree today
On Thu, 6 Mar 2014, Stephen Rothwell wrote:
>
> I have reverted that commit for today.
>
> I suspect that this whole series may need more review and work.
Toss the bits that do not build for now. These can then be handled in
individual patches since the overall framework is present.
--
To unsubs
On Fri, 7 Mar 2014 11:57:44 +1100 Stephen Rothwell
wrote:
> Hi Andrew,
>
> On Thu, 6 Mar 2014 13:48:48 -0800 Andrew Morton
> wrote:
> >
> > Yes, I've disabled the whole series for now. Some of these errors
> > appear to be caused by compiler mishandling, so it's going to be
> > difficult :(
Hi Andrew,
On Thu, 6 Mar 2014 13:48:48 -0800 Andrew Morton
wrote:
>
> Yes, I've disabled the whole series for now. Some of these errors
> appear to be caused by compiler mishandling, so it's going to be
> difficult :(
So, by "the whole series" do you mean just/all these:
percpu-add-raw_cpu_op
On Thu, 6 Mar 2014 19:22:34 +1100 Stephen Rothwell
wrote:
> Hi Andrew,
>
> After merging the akpm tree, today's linux-next build (sparc64 defconfig)
> failed like this:
>
> arch/sparc/kernel/time_64.c: In function 'timer_interrupt':
> arch/sparc/kernel/time_64.c:735:28: error: lvalue required
Hi Andrew,
After merging the akpm tree, today's linux-next build (sparc64 defconfig)
failed like this:
arch/sparc/kernel/time_64.c: In function 'timer_interrupt':
arch/sparc/kernel/time_64.c:735:28: error: lvalue required as increment operand
arch/sparc/kernel/traps_64.c: In function '__cheetah_f
1 - 100 of 170 matches
Mail list logo
