* Re: Next July 29 : Hugetlb test failure (OOPS free_hugepte_range)
From: Sachin Sant @ 2009-08-06 4:40 UTC (permalink / raw)
To: Benjamin Herrenschmidt; +Cc: Stephen Rothwell, linux-next, linuxppc-dev
In-Reply-To: <1249530754.18245.71.camel@pasglop>
Benjamin Herrenschmidt wrote:
> Does this patch fixes it ?
>
> [PATCH] powerpc/mm: Fix encoding of page table cache numbers
>
> The mask used to encode the page table cache number in the
> batch when freeing page tables was too small for the new
> possible values of MMU page sizes. This increases it along
> with a comment explaining the constraints.
>
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> ---
>
Yes this patch fixed the issue for me. Thanks Ben.
Tested-by: Sachin Sant <sachinp@in.ibm.com>
Regards
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
^ permalink raw reply
* Re: Next July 29 : Hugetlb test failure (OOPS free_hugepte_range)
From: Benjamin Herrenschmidt @ 2009-08-06 3:52 UTC (permalink / raw)
To: Sachin Sant; +Cc: Stephen Rothwell, linux-next, linuxppc-dev
In-Reply-To: <4A796237.6070302@in.ibm.com>
On Wed, 2009-08-05 at 16:13 +0530, Sachin Sant wrote:
> Benjamin Herrenschmidt wrote:
> > Thanks. I'll have a look next week. I think when I changed the indices
> > I may have forgotten to update something.
> >
> Ben,
>
> I can recreate this issue with today's next.
> Let me know if i can help in any way to fix this issue.
Does this patch fixes it ?
[PATCH] powerpc/mm: Fix encoding of page table cache numbers
The mask used to encode the page table cache number in the
batch when freeing page tables was too small for the new
possible values of MMU page sizes. This increases it along
with a comment explaining the constraints.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
---
arch/powerpc/include/asm/pgalloc.h | 7 ++++++-
1 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/arch/powerpc/include/asm/pgalloc.h b/arch/powerpc/include/asm/pgalloc.h
index 34b0806..f2e812d 100644
--- a/arch/powerpc/include/asm/pgalloc.h
+++ b/arch/powerpc/include/asm/pgalloc.h
@@ -28,7 +28,12 @@ typedef struct pgtable_free {
unsigned long val;
} pgtable_free_t;
-#define PGF_CACHENUM_MASK 0x7
+/* This needs to be big enough to allow for MMU_PAGE_COUNT + 2 to be stored
+ * and small enough to fit in the low bits of any naturally aligned page
+ * table cache entry. Arbitrarily set to 0x1f, that should give us some
+ * room to grow
+ */
+#define PGF_CACHENUM_MASK 0x1f
static inline pgtable_free_t pgtable_free_cache(void *p, int cachenum,
unsigned long mask)
--
1.6.0.4
> Thanks
> -Sachin
>
> >> : ------------[ cut here ]------------
> >> cpu 0x0: Vector: 700 (Program Check) at [c000000038923560]
> >> pc: c0000000000486d4: .free_hugepte_range+0x68/0xa0
> >> lr: c000000000048954: .hugetlb_free_pgd_range+0x248/0x38c
> >> sp: c0000000389237e0
> >> msr: 8000000000029032
> >> current = 0xc00000003b1d7780
> >> paca = 0xc000000001002400
> >> pid = 2839, comm = readback
> >> kernel BUG at /home/linux-2.6.31-rc4/arch/powerpc/include/asm/pgalloc.h:36!
> >> enter ? for help
> >> [c000000038923880] c000000000048954 .hugetlb_free_pgd_range+0x248/0x38c
> >> [c000000038923970] c000000000165a48 .free_pgtables+0xa0/0x154
> >> [c000000038923a30] c000000000167f78 .exit_mmap+0x13c/0x1cc
> >> [c000000038923ae0] c0000000000997ec .mmput+0x68/0x14c
> >> [c000000038923b70] c00000000009f1d4 .exit_mm+0x190/0x1b8
> >> [c000000038923c20] c0000000000a16e8 .do_exit+0x214/0x784
> >> [c000000038923d00] c0000000000a1d1c .do_group_exit+0xc4/0xf8
> >> [c000000038923da0] c0000000000a1d7c .SyS_exit_group+0x2c/0x48
> >> [c000000038923e30] c0000000000085b4 syscall_exit+0x0/0x40
> >> --- Exception: c01 (System Call) at 000000000fe15038
> >> SP (ffb8e030) is in userspace
> >> 0:mon> e
> >> cpu 0x0: Vector: 700 (Program Check) at [c000000038923560]
> >> pc: c0000000000486d4: .free_hugepte_range+0x68/0xa0
> >> lr: c000000000048954: .hugetlb_free_pgd_range+0x248/0x38c
> >> sp: c0000000389237e0
> >> msr: 8000000000029032
> >> current = 0xc00000003b1d7780
> >> paca = 0xc000000001002400
> >> pid = 2839, comm = readback
> >> kernel BUG at /home/linux-2.6.31-rc4/arch/powerpc/include/asm/pgalloc.h:36!
> >> 0:mon> r
> >> R00 = 0000000000000001 R16 = 0000000000000000
> >> R01 = c0000000389237e0 R17 = 0000000000000001
> >> R02 = c000000000f165a8 R18 = 000000003fffffff
> >> R03 = c0000000014504d0 R19 = 0000000000000000
> >> R04 = c000000039390001 R20 = 0000000000000000
> >> R05 = 0000000000000007 R21 = 0000010000000000
> >> R06 = 0000000000000000 R22 = 0000000040000000
> >> R07 = 0000000040000000 R23 = c0000000014504d0
> >> R08 = c00000003d708188 R24 = 000000003fffffff
> >> R09 = c00000003eb40000 R25 = 0000000000000007
> >> R10 = c00000003d708188 R26 = c00000003ebd41b8
> >> R11 = 0000000000000018 R27 = c0000000014504d0
> >> R12 = 0000000040000448 R28 = c00000003eb40018
> >> R13 = c000000001002400 R29 = 0000000000000008
> >> R14 = 00000000ffffffff R30 = 0000000040000000
> >> R15 = 00000000ffffffff R31 = c0000000389237e0
> >> pc = c0000000000486d4 .free_hugepte_range+0x68/0xa0
> >> lr = c000000000048954 .hugetlb_free_pgd_range+0x248/0x38c
> >> msr = 8000000000029032 cr = 20042444
> >> ctr = 800000000000b6f4 xer = 0000000000000001 trap = 700
> >> 0:mon>
> >>
> >> Line 36 of arch/powerpc/include/asm/pgalloc.h corresponds to
> >>
> >> BUG_ON(cachenum > PGF_CACHENUM_MASK);
> >>
> >> May be something to do with number of elements in huge_pgtable_cache_name ??
> >>
> >> Thanks
> >> -Sachin
^ permalink raw reply related
* Re: linux-next: tty tree build warning
From: Stephen Rothwell @ 2009-08-06 0:12 UTC (permalink / raw)
To: Greg KH; +Cc: linux-next, linux-kernel, Alan Cox
In-Reply-To: <20090805165931.GA4828@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 257 bytes --]
Hi Greg,
On Wed, 5 Aug 2009 09:59:31 -0700 Greg KH <greg@kroah.com> wrote:
>
> I've now fixed this and pushed out the changes.
OK, thanks.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply
* Re: [PATCH -next] isdn: fix netjet build errors
From: David Miller @ 2009-08-05 19:03 UTC (permalink / raw)
To: randy.dunlap; +Cc: sfr, isdn, linux-next, linux-kernel, akpm
In-Reply-To: <20090805092635.6e6df57e.randy.dunlap@oracle.com>
From: Randy Dunlap <randy.dunlap@oracle.com>
Date: Wed, 5 Aug 2009 09:26:35 -0700
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> Fix netjet driver link errors when ISDN_I4L is not enabled:
>
> drivers/built-in.o: In function `mode_tiger':
> netjet.c:(.text+0x325dc8): undefined reference to `isdnhdlc_rcv_init'
> netjet.c:(.text+0x325dd5): undefined reference to `isdnhdlc_out_init'
> drivers/built-in.o: In function `fill_dma':
> netjet.c:(.text+0x325fb6): undefined reference to `isdnhdlc_encode'
> drivers/built-in.o: In function `read_dma':
> netjet.c:(.text+0x32631a): undefined reference to `isdnhdlc_decode'
> drivers/built-in.o: In function `nj_irq':
> netjet.c:(.text+0x326e01): undefined reference to `isdnhdlc_encode'
>
> or move isdnhdlc.c to some other sub-dir..
>
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Thanks Randy.
Karsten, let me know if you want me to apply this directly to
net-next-2.6 or if you want to fix it differently or send it
with other changes you have pending.
Thanks!
^ permalink raw reply
* Re: tty tree change for linux-next
From: Greg KH @ 2009-08-05 17:08 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next, LKML
In-Reply-To: <20090802091605.eeebc7fa.sfr@canb.auug.org.au>
On Sun, Aug 02, 2009 at 09:16:05AM +1000, Stephen Rothwell wrote:
> Hi Greg,
>
> On Sat, 1 Aug 2009 10:18:15 -0700 Greg KH <greg@kroah.com> wrote:
> >
> > Ok, that's not good at all, I just took the patches straight from Alan.
> > I'll edit them up this weekend to work better (i.e. in the format that
> > all of my other patches are in, pseudo-mbox headers, which both quilt
> > and git seem to like.)
>
> Thanks.
This should now be all fixed up. If you happen to notice any I missed,
please let me know.
thanks,
greg k-h
^ permalink raw reply
* Re: linux-next: tty tree build warning
From: Greg KH @ 2009-08-05 16:59 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next, linux-kernel, Alan Cox
In-Reply-To: <20090805132914.GA6054@kroah.com>
On Wed, Aug 05, 2009 at 06:29:14AM -0700, Greg KH wrote:
> On Wed, Aug 05, 2009 at 05:16:06PM +1000, Stephen Rothwell wrote:
> > Hi Greg,
> >
> > Today's linux-next build (powerpc allyesconfig) produced this warning:
> >
> > drivers/char/cyclades.c:3112: warning: initialization from incompatible pointer type
> > drivers/char/cyclades.c:3118: warning: initialization from incompatible pointer type
> >
> > Introduced by commit 46075a6e64b5e4e96079ea273781a1ba366d8244
> > ("tty-cyclades-port-close").
>
> Odd, I haven't changed anything there. I'll check to see what happened.
I've now fixed this and pushed out the changes.
thanks,
greg k-h
^ permalink raw reply
* [PATCH -next] isdn: fix netjet build errors
From: Randy Dunlap @ 2009-08-05 16:26 UTC (permalink / raw)
To: Stephen Rothwell, Karsten Keil; +Cc: linux-next, LKML, akpm
In-Reply-To: <20090805172337.b0688db1.sfr@canb.auug.org.au>
From: Randy Dunlap <randy.dunlap@oracle.com>
Fix netjet driver link errors when ISDN_I4L is not enabled:
drivers/built-in.o: In function `mode_tiger':
netjet.c:(.text+0x325dc8): undefined reference to `isdnhdlc_rcv_init'
netjet.c:(.text+0x325dd5): undefined reference to `isdnhdlc_out_init'
drivers/built-in.o: In function `fill_dma':
netjet.c:(.text+0x325fb6): undefined reference to `isdnhdlc_encode'
drivers/built-in.o: In function `read_dma':
netjet.c:(.text+0x32631a): undefined reference to `isdnhdlc_decode'
drivers/built-in.o: In function `nj_irq':
netjet.c:(.text+0x326e01): undefined reference to `isdnhdlc_encode'
or move isdnhdlc.c to some other sub-dir..
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
drivers/isdn/hardware/mISDN/Kconfig | 1 +
1 file changed, 1 insertion(+)
--- linux-next-20090805.orig/drivers/isdn/hardware/mISDN/Kconfig
+++ linux-next-20090805/drivers/isdn/hardware/mISDN/Kconfig
@@ -78,6 +78,7 @@ config MISDN_NETJET
depends on PCI
select MISDN_IPAC
select ISDN_HDLC
+ select ISDN_I4L # so that make will recurse into sub-dir.
help
Enable support for Traverse Technologies NETJet PCI cards.
---
~Randy
LPC 2009, Sept. 23-25, Portland, Oregon
http://linuxplumbersconf.org/2009/
^ permalink raw reply
* Re: Next July 29 : Hugetlb test failure (OOPS free_hugepte_range)
From: Sachin Sant @ 2009-08-05 15:33 UTC (permalink / raw)
To: Kumar Gala; +Cc: Stephen Rothwell, linuxppc-dev, linux-next
In-Reply-To: <E0A64FA0-C835-4361-A203-E9CB5377599C@kernel.crashing.org>
Kumar Gala wrote:
>
> On Jul 29, 2009, at 10:04 AM, Sachin Sant wrote:
>
>> While executing hugetlb tests against today's Next tree on
>> a Power 6 box came across following OOPS.
>
> out of interest what tests are you running for hugetlb?
The one maintained at : http://libhugetlbfs.ozlabs.org/ which points
to the sourceforge libhugetlbfs project.
Latest release can be downloaded from sourceforge using
http://sourceforge.net/projects/libhugetlbfs/files/
I am using version 2.5
Thanks
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
^ permalink raw reply
* Re: Next July 29 : Hugetlb test failure (OOPS free_hugepte_range)
From: Kumar Gala @ 2009-08-05 14:35 UTC (permalink / raw)
To: Sachin Sant; +Cc: Stephen Rothwell, linuxppc-dev, linux-next
In-Reply-To: <4A706504.6040704@in.ibm.com>
On Jul 29, 2009, at 10:04 AM, Sachin Sant wrote:
> While executing hugetlb tests against today's Next tree on
> a Power 6 box came across following OOPS.
out of interest what tests are you running for hugetlb?
- k
^ permalink raw reply
* Re: linux-next: tty tree build warning
From: Greg KH @ 2009-08-05 13:29 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next, linux-kernel, Alan Cox
In-Reply-To: <20090805171606.d3d3877c.sfr@canb.auug.org.au>
On Wed, Aug 05, 2009 at 05:16:06PM +1000, Stephen Rothwell wrote:
> Hi Greg,
>
> Today's linux-next build (powerpc allyesconfig) produced this warning:
>
> drivers/char/cyclades.c:3112: warning: initialization from incompatible pointer type
> drivers/char/cyclades.c:3118: warning: initialization from incompatible pointer type
>
> Introduced by commit 46075a6e64b5e4e96079ea273781a1ba366d8244
> ("tty-cyclades-port-close").
Odd, I haven't changed anything there. I'll check to see what happened.
thanks,
greg k-h
^ permalink raw reply
* Re: linux-next: Tree for August 5
From: Boaz Harrosh @ 2009-08-05 13:28 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next, LKML, ppc-dev
In-Reply-To: <20090805201336.fd2de2ad.sfr@canb.auug.org.au>
On 08/05/2009 01:13 PM, Stephen Rothwell wrote:
> Hi Boaz,
>
> On Wed, 05 Aug 2009 11:11:20 +0300 Boaz Harrosh <bharrosh@panasas.com> wrote:
>>
>> On 08/05/2009 10:23 AM, Stephen Rothwell wrote:
>>>
>>> This tree fails to build for powerpc allyesconfig (final link problem).
>>
>> Above is reported for a long time. Is it related to this:
>> http://www.spinics.net/lists/kernel/msg921978.html
>
> No, it is this:
>
> powerpc-linux-ld: TOC section size exceeds 64k
>
> It is powerpc specific and the only way we can think of fixing it
> involves stopping building the built-in.o files and linking the entire
> kernel in one go at the end. We just haven't had time (or the energy) to
> try to fix it properly while it only affects the final link of the
> allyesconfig kernel.
>
Ha, OK allyesconfig. Last time I attempted an allyesconfig for i386 I got
me the OOM killer attack on my KDE, half way into the final link.
That's why I use allmodconfig for when I need "try to compile everything ++"
I get just as much compilation coverage if not more. And is faster.
It'll not show symbol conflicts if any exist, though.
Thanks
Boaz
^ permalink raw reply
* Re: Next July 29 : Hugetlb test failure (OOPS free_hugepte_range)
From: Sachin Sant @ 2009-08-05 10:43 UTC (permalink / raw)
To: Benjamin Herrenschmidt; +Cc: Stephen Rothwell, linux-next, linuxppc-dev
In-Reply-To: <1248957028.1509.85.camel@pasglop>
Benjamin Herrenschmidt wrote:
> Thanks. I'll have a look next week. I think when I changed the indices
> I may have forgotten to update something.
>
Ben,
I can recreate this issue with today's next.
Let me know if i can help in any way to fix this issue.
Thanks
-Sachin
>> : ------------[ cut here ]------------
>> cpu 0x0: Vector: 700 (Program Check) at [c000000038923560]
>> pc: c0000000000486d4: .free_hugepte_range+0x68/0xa0
>> lr: c000000000048954: .hugetlb_free_pgd_range+0x248/0x38c
>> sp: c0000000389237e0
>> msr: 8000000000029032
>> current = 0xc00000003b1d7780
>> paca = 0xc000000001002400
>> pid = 2839, comm = readback
>> kernel BUG at /home/linux-2.6.31-rc4/arch/powerpc/include/asm/pgalloc.h:36!
>> enter ? for help
>> [c000000038923880] c000000000048954 .hugetlb_free_pgd_range+0x248/0x38c
>> [c000000038923970] c000000000165a48 .free_pgtables+0xa0/0x154
>> [c000000038923a30] c000000000167f78 .exit_mmap+0x13c/0x1cc
>> [c000000038923ae0] c0000000000997ec .mmput+0x68/0x14c
>> [c000000038923b70] c00000000009f1d4 .exit_mm+0x190/0x1b8
>> [c000000038923c20] c0000000000a16e8 .do_exit+0x214/0x784
>> [c000000038923d00] c0000000000a1d1c .do_group_exit+0xc4/0xf8
>> [c000000038923da0] c0000000000a1d7c .SyS_exit_group+0x2c/0x48
>> [c000000038923e30] c0000000000085b4 syscall_exit+0x0/0x40
>> --- Exception: c01 (System Call) at 000000000fe15038
>> SP (ffb8e030) is in userspace
>> 0:mon> e
>> cpu 0x0: Vector: 700 (Program Check) at [c000000038923560]
>> pc: c0000000000486d4: .free_hugepte_range+0x68/0xa0
>> lr: c000000000048954: .hugetlb_free_pgd_range+0x248/0x38c
>> sp: c0000000389237e0
>> msr: 8000000000029032
>> current = 0xc00000003b1d7780
>> paca = 0xc000000001002400
>> pid = 2839, comm = readback
>> kernel BUG at /home/linux-2.6.31-rc4/arch/powerpc/include/asm/pgalloc.h:36!
>> 0:mon> r
>> R00 = 0000000000000001 R16 = 0000000000000000
>> R01 = c0000000389237e0 R17 = 0000000000000001
>> R02 = c000000000f165a8 R18 = 000000003fffffff
>> R03 = c0000000014504d0 R19 = 0000000000000000
>> R04 = c000000039390001 R20 = 0000000000000000
>> R05 = 0000000000000007 R21 = 0000010000000000
>> R06 = 0000000000000000 R22 = 0000000040000000
>> R07 = 0000000040000000 R23 = c0000000014504d0
>> R08 = c00000003d708188 R24 = 000000003fffffff
>> R09 = c00000003eb40000 R25 = 0000000000000007
>> R10 = c00000003d708188 R26 = c00000003ebd41b8
>> R11 = 0000000000000018 R27 = c0000000014504d0
>> R12 = 0000000040000448 R28 = c00000003eb40018
>> R13 = c000000001002400 R29 = 0000000000000008
>> R14 = 00000000ffffffff R30 = 0000000040000000
>> R15 = 00000000ffffffff R31 = c0000000389237e0
>> pc = c0000000000486d4 .free_hugepte_range+0x68/0xa0
>> lr = c000000000048954 .hugetlb_free_pgd_range+0x248/0x38c
>> msr = 8000000000029032 cr = 20042444
>> ctr = 800000000000b6f4 xer = 0000000000000001 trap = 700
>> 0:mon>
>>
>> Line 36 of arch/powerpc/include/asm/pgalloc.h corresponds to
>>
>> BUG_ON(cachenum > PGF_CACHENUM_MASK);
>>
>> May be something to do with number of elements in huge_pgtable_cache_name ??
>>
>> Thanks
>> -Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
^ permalink raw reply
* Re: linux-next: Tree for August 5
From: Stephen Rothwell @ 2009-08-05 10:13 UTC (permalink / raw)
To: Boaz Harrosh; +Cc: linux-next, ppc-dev, LKML
In-Reply-To: <4A793EA8.50306@panasas.com>
[-- Attachment #1.1: Type: text/plain, Size: 832 bytes --]
Hi Boaz,
On Wed, 05 Aug 2009 11:11:20 +0300 Boaz Harrosh <bharrosh@panasas.com> wrote:
>
> On 08/05/2009 10:23 AM, Stephen Rothwell wrote:
> >
> > This tree fails to build for powerpc allyesconfig (final link problem).
>
> Above is reported for a long time. Is it related to this:
> http://www.spinics.net/lists/kernel/msg921978.html
No, it is this:
powerpc-linux-ld: TOC section size exceeds 64k
It is powerpc specific and the only way we can think of fixing it
involves stopping building the built-in.o files and linking the entire
kernel in one go at the end. We just haven't had time (or the energy) to
try to fix it properly while it only affects the final link of the
allyesconfig kernel.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #1.2: Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 150 bytes --]
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
^ permalink raw reply
* Re: [PATCH] serial167: Read buffer overflow
From: Geert Uytterhoeven @ 2009-08-05 9:17 UTC (permalink / raw)
To: Andrew Morton; +Cc: Roel Kluin, alan, linux-kernel, linux-next, Linux/m68k
In-Reply-To: <20090804151838.c5cb362b.akpm@linux-foundation.org>
On Wed, Aug 5, 2009 at 00:18, Andrew Morton<akpm@linux-foundation.org> wrote:
> btw, m68k allmodconfig in current mainline is sick:
>
> And in linux-next m68k allmodconfig is dead as a doornail:
Will look at it (eventually)...
But recovering from a too-long absence and replacing the computer that
died before the absence
while keeping the mill of life running take its time...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
^ permalink raw reply
* Re: linux-next: Tree for August 5
From: Boaz Harrosh @ 2009-08-05 8:11 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next, LKML
In-Reply-To: <20090805172337.b0688db1.sfr@canb.auug.org.au>
On 08/05/2009 10:23 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20090804:
>
> This tree fails to build for powerpc allyesconfig (final link problem).
>
Above is reported for a long time. Is it related to this:
http://www.spinics.net/lists/kernel/msg921978.html
> The mfd tree gained a conflict against the input tree.
>
> The drm tree gained a conflict against Linus' tree.
>
> The edac-amd tree gained a conflict against Linus' tree.
>
> ----------------------------------------------------------------------------
>
<snip>
^ permalink raw reply
* Re: Rebasing the edac-amd tree (Was: Re: linux-next: manual merge of the edac-amd tree with Linus' tree)
From: Borislav Petkov @ 2009-08-05 7:42 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: Borislav Petkov, linux-next, linux-kernel, Ingo Molnar
In-Reply-To: <20090805164032.3cf9d95a.sfr@canb.auug.org.au>
Hi,
On Wed, Aug 05, 2009 at 04:40:32PM +1000, Stephen Rothwell wrote:
> On Wed, 5 Aug 2009 08:22:15 +0200 Borislav Petkov <petkovbb@googlemail.com> wrote:
> >
> > thanks and yes, you're right. The former patch is less intrusive
> > and we opted for that one since it is really late in the -rc cycle
> > but the latter cleans up stuff so that code flow becomes much more
> > understandable. I'll rediff later and sorry for the inconvenience.
>
> As an alternative to rebasing, you could merge Linus' current tree into
> yours and do the merge fixup there. This is not particularly necessary,
> as the fixup is fairly simple. Though you may want to do that sometime
> before you ask Linus to merge your tree.
that's what I'd normally do but I'm carrying some more patches which
have to go to -tip and I'd rather rebase to have a clean history and
all.
> > By the way, I see that you're merging edac-amd before tip and I'm going
> > to need to rebase my tree against tip in the next couple of days since
> > it depends on a bunch of stuff in it, so could you please switch the
> > merge order of the two trees so that edac-amd goes after tip?
>
> Again, instead of rebasing, you could just merge in the branches from tip
> that you depend on. You need to make sure that you only depend on stable
> (i.e. non rebasing) branches in the tip tree, not on the branch
> (auto-latest) that is actually merged into linux-next. Please discuss
> this with Ingo.
Yep, it happened yesterday.
>
> I will move the edac-amd tree to after the tip tree tomorrow.
Thanks.
--
Regards/Gruss,
Boris.
^ permalink raw reply
* linux-next: Tree for August 5
From: Stephen Rothwell @ 2009-08-05 7:23 UTC (permalink / raw)
To: linux-next; +Cc: LKML
[-- Attachment #1: Type: text/plain, Size: 8358 bytes --]
Hi all,
Changes since 20090804:
This tree fails to build for powerpc allyesconfig (final link problem).
The mfd tree gained a conflict against the input tree.
The drm tree gained a conflict against Linus' tree.
The edac-amd tree gained a conflict against Linus' tree.
----------------------------------------------------------------------------
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
(patches at
http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/). If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one. You should use "git fetch" as mentioned in the FAQ on the wiki
(see below).
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was built with
a ppc64_defconfig for powerpc and an allmodconfig for x86_64. After the
final fixups (if any), it is also built with powerpc allnoconfig (32 and
64 bit), ppc44x_defconfig and allyesconfig (minus
CONFIG_PROFILE_ALL_BRANCHES) and i386, sparc and sparc64 defconfig.
These builds also have CONFIG_ENABLE_WARN_DEPRECATED,
CONFIG_ENABLE_MUST_CHECK and CONFIG_DEBUG_INFO disabled when necessary.
Below is a summary of the state of the merge.
We are up to 138 trees (counting Linus' and 20 trees of patches pending for
Linus' tree), more are welcome (even if they are currently empty).
Thanks to those who have contributed, and to those who haven't, please do.
Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next . If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.
Thanks to Jan Dittmer for adding the linux-next tree to his build tests
at http://l4x.org/k/ , the guys at http://test.kernel.org/ and Randy
Dunlap for doing many randconfig builds.
There is a wiki covering stuff to do with linux-next at
http://linux.f-seidel.de/linux-next/pmwiki/ . Thanks to Frank Seidel.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
$ git checkout master
$ git reset --hard stable
Merging origin/master
Merging fixes/fixes
Merging arm-current/master
Merging m68k-current/for-linus
Merging powerpc-merge/merge
Merging sparc-current/master
Merging scsi-rc-fixes/master
Merging net-current/master
Merging sound-current/for-linus
Merging pci-current/for-linus
Merging wireless-current/master
Merging kbuild-current/master
Merging quilt/driver-core.current
Merging quilt/tty.current
Merging quilt/usb.current
Merging cpufreq-current/fixes
Merging input-current/for-linus
Merging md-current/for-linus
Merging audit-current/for-linus
Merging crypto-current/master
Merging dwmw2/master
Merging arm/devel
CONFLICT (content): Merge conflict in MAINTAINERS
Merging davinci/for-next
Merging pxa/for-next
CONFLICT (content): Merge conflict in MAINTAINERS
Merging thumb-2/thumb-2
Merging avr32/avr32-arch
Merging blackfin/for-linus
Merging cris/for-next
Merging ia64/test
Merging m68k/for-next
Merging m68knommu/for-next
Merging microblaze/next
Merging mips/mips-for-linux-next
CONFLICT (content): Merge conflict in arch/mips/cavium-octeon/dma-octeon.c
CONFLICT (add/add): Merge conflict in arch/mips/cavium-octeon/executive/cvmx-helper-errata.c
CONFLICT (content): Merge conflict in arch/mips/mm/tlbex.c
CONFLICT (content): Merge conflict in arch/mips/sibyte/swarm/setup.c
CONFLICT (content): Merge conflict in drivers/char/hw_random/Kconfig
CONFLICT (content): Merge conflict in drivers/char/hw_random/Makefile
CONFLICT (add/add): Merge conflict in drivers/dma/txx9dmac.c
Merging parisc/next
Merging powerpc/next
Merging 4xx/next
Merging galak/next
Merging s390/features
Merging sh/master
Merging sparc/master
Merging xtensa/master
Merging cifs/master
Merging configfs/linux-next
CONFLICT (content): Merge conflict in fs/configfs/dir.c
Merging ecryptfs/next
Merging ext3/for_next
Merging ext4/next
Merging fatfs/master
Merging fuse/for-next
Merging gfs2/master
Merging jfs/next
Merging nfs/linux-next
Merging nfsd/nfsd-next
Merging nilfs2/for-next
Merging ocfs2/linux-next
Merging squashfs/master
Merging v9fs/for-next
Merging ubifs/linux-next
Merging xfs/master
Merging reiserfs-bkl/reiserfs/kill-bkl
Merging vfs/for-next
Merging pci/linux-next
Merging hid/for-next
Merging quilt/i2c
Merging quilt/jdelvare-hwmon
Merging quilt/kernel-doc
Merging v4l-dvb/master
CONFLICT (content): Merge conflict in arch/arm/mach-davinci/board-dm646x-evm.c
CONFLICT (content): Merge conflict in arch/arm/mach-davinci/dm355.c
CONFLICT (content): Merge conflict in arch/arm/mach-davinci/dm644x.c
CONFLICT (content): Merge conflict in arch/arm/mach-davinci/dm646x.c
CONFLICT (content): Merge conflict in arch/arm/mach-davinci/include/mach/dm355.h
CONFLICT (content): Merge conflict in arch/arm/mach-davinci/include/mach/dm644x.h
Merging quota/for_next
Merging kbuild/master
Merging ide/master
Merging libata/NEXT
Merging infiniband/for-next
Merging acpi/test
Merging ieee1394/for-next
Merging ubi/linux-next
Merging kvm/master
Merging dlm/next
Merging scsi/master
Merging async_tx/next
Merging udf/for_next
Merging net/master
Merging wireless/master
Merging mtd/master
Merging crypto/master
Merging sound/for-next
Merging cpufreq/next
Merging quilt/rr
CONFLICT (content): Merge conflict in arch/x86/lguest/boot.c
CONFLICT (content): Merge conflict in drivers/lguest/page_tables.c
CONFLICT (content): Merge conflict in drivers/virtio/virtio_pci.c
[master 0479a8a] Revert "cpumask:remove-set_cpus_allowed"
Merging mmc/next
Merging input/next
Merging lsm/for-next
Merging block/for-next
Merging quilt/device-mapper
Merging embedded/master
Merging firmware/master
Merging pcmcia/master
Merging battery/master
Merging leds/for-mm
Merging backlight/for-mm
Merging kgdb/kgdb-next
Merging slab/for-next
Merging uclinux/for-next
Merging md/for-next
Merging mfd/for-next
CONFLICT (content): Merge conflict in drivers/input/misc/Kconfig
Merging hdlc/hdlc-next
Merging drm/drm-next
CONFLICT (content): Merge conflict in drivers/gpu/drm/drm_crtc.c
Merging voltage/for-next
Merging security-testing/next
Merging lblnet/master
Merging agp/agp-next
Merging uwb/for-upstream
Merging watchdog/master
Merging bdev/master
Merging dwmw2-iommu/master
Merging cputime/cputime
Merging osd/linux-next
Merging jc_docs/docs-next
Merging nommu/master
Merging trivial/for-next
CONFLICT (content): Merge conflict in MAINTAINERS
Merging audit/for-next
Merging omap/for-next
Merging quilt/aoe
Merging suspend/linux-next
Merging bluetooth/master
Merging edac-amd/for-next
CONFLICT (content): Merge conflict in arch/x86/lib/msr.c
CONFLICT (content): Merge conflict in drivers/edac/amd64_edac.c
Merging fsnotify/for-next
Merging irda/for-next
Merging hwlat/for-linus
Merging drbd/drbd
Applying: drbd: fix for removal of blk_queue_stack_limits
Merging kmemleak/kmemleak
Merging tip/auto-latest
CONFLICT (content): Merge conflict in include/linux/rcupdate.h
CONFLICT (content): Merge conflict in kernel/fork.c
Merging oprofile/for-next
Merging percpu/for-next
CONFLICT (content): Merge conflict in arch/sh/kernel/vmlinux.lds.S
CONFLICT (content): Merge conflict in arch/x86/kernel/cpu/perf_counter.c
CONFLICT (content): Merge conflict in drivers/cpufreq/cpufreq_ondemand.c
Merging sfi/sfi-test
Merging asm-generic/next
Merging quilt/driver-core
CONFLICT (content): Merge conflict in init/main.c
Merging quilt/tty
CONFLICT (content): Merge conflict in arch/x86/include/asm/termios.h
CONFLICT (content): Merge conflict in drivers/char/tty_ldisc.c
Merging quilt/usb
CONFLICT (content): Merge conflict in drivers/usb/gadget/m66592-udc.c
CONFLICT (content): Merge conflict in drivers/usb/host/r8a66597-hcd.c
Merging quilt/staging
CONFLICT (delete/modify): drivers/staging/epl/VirtualEthernetLinux.c deleted in quilt/staging and modified in HEAD. Version HEAD of drivers/staging/epl/VirtualEthernetLinux.c left in tree.
$ git rm -f drivers/staging/epl/VirtualEthernetLinux.c
Merging scsi-post-merge/master
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply
* linux-next: tty tree build warning
From: Stephen Rothwell @ 2009-08-05 7:16 UTC (permalink / raw)
To: Greg KH; +Cc: linux-next, linux-kernel, Alan Cox
[-- Attachment #1: Type: text/plain, Size: 462 bytes --]
Hi Greg,
Today's linux-next build (powerpc allyesconfig) produced this warning:
drivers/char/cyclades.c:3112: warning: initialization from incompatible pointer type
drivers/char/cyclades.c:3118: warning: initialization from incompatible pointer type
Introduced by commit 46075a6e64b5e4e96079ea273781a1ba366d8244
("tty-cyclades-port-close").
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply
* Rebasing the edac-amd tree (Was: Re: linux-next: manual merge of the edac-amd tree with Linus' tree)
From: Stephen Rothwell @ 2009-08-05 6:40 UTC (permalink / raw)
To: Borislav Petkov; +Cc: Borislav Petkov, linux-next, linux-kernel, Ingo Molnar
In-Reply-To: <20090805062215.GA7732@liondog.tnic>
[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]
Hi Boris,
On Wed, 5 Aug 2009 08:22:15 +0200 Borislav Petkov <petkovbb@googlemail.com> wrote:
>
> thanks and yes, you're right. The former patch is less intrusive
> and we opted for that one since it is really late in the -rc cycle
> but the latter cleans up stuff so that code flow becomes much more
> understandable. I'll rediff later and sorry for the inconvenience.
As an alternative to rebasing, you could merge Linus' current tree into
yours and do the merge fixup there. This is not particularly necessary,
as the fixup is fairly simple. Though you may want to do that sometime
before you ask Linus to merge your tree.
> By the way, I see that you're merging edac-amd before tip and I'm going
> to need to rebase my tree against tip in the next couple of days since
> it depends on a bunch of stuff in it, so could you please switch the
> merge order of the two trees so that edac-amd goes after tip?
Again, instead of rebasing, you could just merge in the branches from tip
that you depend on. You need to make sure that you only depend on stable
(i.e. non rebasing) branches in the tip tree, not on the branch
(auto-latest) that is actually merged into linux-next. Please discuss
this with Ingo.
I will move the edac-amd tree to after the tip tree tomorrow.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply
* Re: linux-next: manual merge of the edac-amd tree with Linus' tree
From: Borislav Petkov @ 2009-08-05 6:22 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: Borislav Petkov, linux-next, linux-kernel, Doug Thompson
In-Reply-To: <20090805150933.103de233.sfr@canb.auug.org.au>
Hi Stephen,
On Wed, Aug 05, 2009 at 03:09:33PM +1000, Stephen Rothwell wrote:
> Today's linux-next merge of the edac-amd tree got a conflict in
> drivers/edac/amd64_edac.c between commit
> 126b67b8d26f6623d199aa59279f2e3243f2144c ("amd64_edac: fix ECC checking")
> from Linus' tree and commit 793a2a12b43aba669c8b2604a45f000a394f142d
> ("amd64_edac: cleanup amd64_check_ecc_enabled") from the edac-amd tree.
>
> I don't think the fix in the former patch is required, so I just used the
> latter version.
thanks and yes, you're right. The former patch is less intrusive
and we opted for that one since it is really late in the -rc cycle
but the latter cleans up stuff so that code flow becomes much more
understandable. I'll rediff later and sorry for the inconvenience.
By the way, I see that you're merging edac-amd before tip and I'm going
to need to rebase my tree against tip in the next couple of days since
it depends on a bunch of stuff in it, so could you please switch the
merge order of the two trees so that edac-amd goes after tip?
Thanks.
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
> http://www.canb.auug.org.au/~sfr/
--
Regards/Gruss,
Boris.
^ permalink raw reply
* linux-next: manual merge of the edac-amd tree with Linus' tree
From: Stephen Rothwell @ 2009-08-05 5:09 UTC (permalink / raw)
To: Borislav Petkov; +Cc: linux-next, linux-kernel, Doug Thompson
[-- Attachment #1: Type: text/plain, Size: 542 bytes --]
Hi Borislav,
Today's linux-next merge of the edac-amd tree got a conflict in
drivers/edac/amd64_edac.c between commit
126b67b8d26f6623d199aa59279f2e3243f2144c ("amd64_edac: fix ECC checking")
from Linus' tree and commit 793a2a12b43aba669c8b2604a45f000a394f142d
("amd64_edac: cleanup amd64_check_ecc_enabled") from the edac-amd tree.
I don't think the fix in the former patch is required, so I just used the
latter version.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply
* linux-next: manual merge of the drm tree with Linus' tree
From: Stephen Rothwell @ 2009-08-05 3:44 UTC (permalink / raw)
To: Dave Airlie; +Cc: linux-next, linux-kernel, Jakob Bornecrantz, Zhao Yakui
Hi Dave,
Today's linux-next merge of the drm tree got a conflict in
drivers/gpu/drm/drm_crtc.c between commit
7781de74568bddfefbd2d32a934a8c791a2420cd ("drm: Small logic fix in
drm_mode_setcrtc") from Linus' tree and commit
58367ed65f30128d8b763bf4c1fb942da49ade15 ("drm: Add the debug info in
generic drm mode by using DRM_DEBUG_KMS") from the drm tree.
Just context changes. I fixed it up (see below) and can carry the fix as
necessary.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
diff --cc drivers/gpu/drm/drm_crtc.c
index 33be210,a8c8311..0000000
--- a/drivers/gpu/drm/drm_crtc.c
+++ b/drivers/gpu/drm/drm_crtc.c
@@@ -1461,8 -1484,8 +1484,8 @@@ int drm_mode_setcrtc(struct drm_device
goto out;
}
- if (crtc_req->count_connectors > 0 && !mode && !fb) {
+ if (crtc_req->count_connectors > 0 && (!mode || !fb)) {
- DRM_DEBUG("Count connectors is %d but no mode or fb set\n",
+ DRM_DEBUG_KMS("Count connectors is %d but no mode or fb set\n",
crtc_req->count_connectors);
ret = -EINVAL;
goto out;
^ permalink raw reply
* linux-next: manual merge of the mfd tree with the input tree
From: Stephen Rothwell @ 2009-08-05 3:31 UTC (permalink / raw)
To: Samuel Ortiz
Cc: linux-next, linux-kernel, Michael Hennerich, Dmitry Torokhov,
Mark Brown
Hi Samuel,
Today's linux-next merge of the mfd tree got a conflict in
drivers/input/misc/Kconfig between commit
4832958218f96f98009c5e01729fbe2b48c7124c ("Input: add Blackfin rotary
input driver") from the input tree and commit
f45c2fa48317249892af5b63f4b35c7c90191df3 ("input: Add support for the
WM831x ON pin") from the mfd tree.
Just overlapping additions. I fixed it up (see below) and can carry the
fix as necessary.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
diff --cc drivers/input/misc/Kconfig
index cbe21bc,c8e7d8a..0000000
--- a/drivers/input/misc/Kconfig
+++ b/drivers/input/misc/Kconfig
@@@ -270,13 -270,14 +270,23 @@@ config INPUT_DM355EV
To compile this driver as a module, choose M here: the
module will be called dm355evm_keys.
+config INPUT_BFIN_ROTARY
+ tristate "Blackfin Rotary support"
+ depends on BF54x || BF52x
+ help
+ Say Y here if you want to use the Blackfin Rotary.
+
+ To compile this driver as a module, choose M here: the
+ module will be called bfin-rotary.
+
+ config INPUT_WM831X_ON
+ tristate "WM831X ON pin"
+ depends on MFD_WM831X
+ help
+ Support the ON pin of WM831X PMICs as an input device
+ reporting power button status.
+
+ To compile this driver as a module, choose M here: the module
+ will be called wm831x_on.
+
endif
^ permalink raw reply
* Re: [PATCH] serial167: Read buffer overflow
From: Andrew Morton @ 2009-08-04 22:18 UTC (permalink / raw)
To: Roel Kluin; +Cc: alan, linux-kernel, Geert Uytterhoeven, linux-next
In-Reply-To: <4A76D4DA.8090905@gmail.com>
On Mon, 03 Aug 2009 14:15:22 +0200
Roel Kluin <roel.kluin@gmail.com> wrote:
> @@ -222,7 +222,7 @@ static inline int serial_paranoia_check(struct cyclades_port *info, char *name,
> }
>
> if ((long)info < (long)(&cy_port[0])
> - || (long)(&cy_port[NR_PORTS]) < (long)info) {
> + || (long)(&cy_port[NR_PORTS-1]) < (long)info) {
> printk("Warning: cyclades_port out of range for (%s) in %s\n",
> name, routine);
OK, that hurts my brain. And all those casts are pointless. How about this?
if (info < &cy_port[0] || info >= &cy_port[NR_PORTS]) {
printk("Warning: cyclades_port out of range for (%s) in %s\n",
name, routine);
return 1;
}
btw, m68k allmodconfig in current mainline is sick:
In file included from /usr/src/devel/arch/m68k/include/asm/pgtable.h:4,
from include/linux/mm.h:40,
from drivers/char/serial167.c:62:
/usr/src/devel/arch/m68k/include/asm/pgtable_mm.h:148:1: warning: "pgprot_noncached" redefined
In file included from /usr/src/devel/arch/m68k/include/asm/pgtable_mm.h:138,
from /usr/src/devel/arch/m68k/include/asm/pgtable.h:4,
from include/linux/mm.h:40,
from drivers/char/serial167.c:62:
include/asm-generic/pgtable.h:133:1: warning: this is the location of the previous definition
And in linux-next m68k allmodconfig is dead as a doornail:
drivers/staging/vme/Kconfig:5:warning: type of 'VME' redefined from 'boolean' to 'tristate'
In file included from include/linux/irq.h:12,
from include/asm-generic/hardirq.h:6,
from /usr/src/devel/arch/m68k/include/asm/hardirq.h:4,
from include/linux/hardirq.h:10,
from /usr/src/devel/arch/m68k/include/asm/system_mm.h:69,
from /usr/src/devel/arch/m68k/include/asm/system.h:4,
from include/linux/list.h:7,
from include/linux/preempt.h:11,
from include/linux/spinlock.h:50,
from include/linux/seqlock.h:29,
from include/linux/time.h:8,
from include/linux/timex.h:56,
from include/linux/sched.h:56,
from arch/m68k/kernel/asm-offsets.c:12:
include/linux/smp.h:17: error: field 'list' has incomplete type
In file included from include/linux/mmzone.h:9,
from include/linux/gfp.h:4,
from include/linux/irq.h:20,
from include/asm-generic/hardirq.h:6,
from /usr/src/devel/arch/m68k/include/asm/hardirq.h:4,
from include/linux/hardirq.h:10,
from /usr/src/devel/arch/m68k/include/asm/system_mm.h:69,
from /usr/src/devel/arch/m68k/include/asm/system.h:4,
from include/linux/list.h:7,
from include/linux/preempt.h:11,
from include/linux/spinlock.h:50,
from include/linux/seqlock.h:29,
from include/linux/time.h:8,
from include/linux/timex.h:56,
from include/linux/sched.h:56,
from arch/m68k/kernel/asm-offsets.c:12:
include/linux/wait.h:37: error: field 'task_list' has incomplete type
include/linux/wait.h:51: error: expected specifier-qualifier-list before 'spinlock_t'
include/linux/wait.h: In function 'waitqueue_active':
include/linux/wait.h:108: error: implicit declaration of function 'list_empty'
include/linux/wait.h:108: error: 'wait_queue_head_t' has no member named 'task_list'
include/linux/wait.h: In function '__add_wait_queue':
include/linux/wait.h:117: error: implicit declaration of function 'list_add'
include/linux/wait.h:117: error: 'wait_queue_head_t' has no member named 'task_list'
include/linux/wait.h: In function '__add_wait_queue_tail':
include/linux/wait.h:126: error: implicit declaration of function 'list_add_tail'
include/linux/wait.h:126: error: 'wait_queue_head_t' has no member named 'task_list'
include/linux/wait.h: In function '__remove_wait_queue':
include/linux/wait.h:132: error: implicit declaration of function 'list_del'
^ permalink raw reply
* Re: linux-next: tip tree build warning
From: Steven Rostedt @ 2009-08-04 16:24 UTC (permalink / raw)
To: Stephen Rothwell
Cc: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra,
linux-next, linux-kernel
In-Reply-To: <20090804161640.70817ee6.sfr@canb.auug.org.au>
On Tue, 2009-08-04 at 16:16 +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next build (powerpc ppc64_defconfig) produced these warnings:
>
> kernel/trace/ring_buffer.c: In function 'rb_head_page_set':
> kernel/trace/ring_buffer.c:704: warning: initialization makes pointer from integer without a cast
> kernel/trace/ring_buffer.c:704: warning: initialization makes pointer from integer without a cast
> kernel/trace/ring_buffer.c: In function 'rb_head_page_replace':
> kernel/trace/ring_buffer.c:797: warning: initialization makes integer from pointer without a cast
>
> Introduced by commit 77ae365eca895061c8bf2b2e3ae1d9ea62869739
> ("ring-buffer: make lockless").
>
Thanks, I'll take a look at it.
-- Steve
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox