Re: linux-next: Tree for Mar 20 (vmcore)

2013-03-20 Thread Stephen Rothwell
Hi David, On Wed, 20 Mar 2013 19:49:09 -0700 (PDT) David Rientjes wrote: > > On Thu, 21 Mar 2013, Stephen Rothwell wrote: > > > What exactly are "these patches" so that I can remove them from my copy > > of the mmotm tree (assuming that Andrew does not get a new mmotm released > > in the next

Re: linux-next: Tree for Mar 20 (vmcore)

2013-03-20 Thread David Rientjes
On Thu, 21 Mar 2013, Stephen Rothwell wrote: > What exactly are "these patches" so that I can remove them from my copy > of the mmotm tree (assuming that Andrew does not get a new mmotm released > in the next hour or so). > [nacked]

Re: linux-next: Tree for Mar 20 (vmcore)

2013-03-20 Thread Stephen Rothwell
Hi, On Wed, 20 Mar 2013 17:10:30 -0700 (PDT) David Rientjes wrote: > > On Wed, 20 Mar 2013, David Rientjes wrote: > > > I don't think that's it, linux/kexec.h already gets included indirectly. > > The problem is that CONFIG_KEXEC isn't set so the definition in kexec.h is > > meaningless. >

Re: linux-next: Tree for Mar 20 (vmcore)

2013-03-20 Thread David Rientjes
On Wed, 20 Mar 2013, David Rientjes wrote: > I don't think that's it, linux/kexec.h already gets included indirectly. > The problem is that CONFIG_KEXEC isn't set so the definition in kexec.h is > meaningless. > > This comes from "vmcore: check NT_VMCORE_PAD as a mark indicating the end > of

Re: linux-next: Tree for Mar 20 (vmcore)

2013-03-20 Thread Randy Dunlap
On 03/20/13 11:56, David Rientjes wrote: > On Wed, 20 Mar 2013, Randy Dunlap wrote: > >> on x86_64: >> >> fs/proc/vmcore.c: In function 'merge_note_headers_elf64': >> fs/proc/vmcore.c:349:22: error: 'VMCOREINFO_NOTE_NAME' undeclared (first use >> in this function) >> fs/proc/vmcore.c:349:22:

Re: linux-next: Tree for Mar 20 (vmcore)

2013-03-20 Thread David Rientjes
On Wed, 20 Mar 2013, Randy Dunlap wrote: > on x86_64: > > fs/proc/vmcore.c: In function 'merge_note_headers_elf64': > fs/proc/vmcore.c:349:22: error: 'VMCOREINFO_NOTE_NAME' undeclared (first use > in this function) > fs/proc/vmcore.c:349:22: note: each undeclared identifier is reported only >

Re: linux-next: Tree for Mar 20 (vmcore)

2013-03-20 Thread David Rientjes
On Wed, 20 Mar 2013, Randy Dunlap wrote: on x86_64: fs/proc/vmcore.c: In function 'merge_note_headers_elf64': fs/proc/vmcore.c:349:22: error: 'VMCOREINFO_NOTE_NAME' undeclared (first use in this function) fs/proc/vmcore.c:349:22: note: each undeclared identifier is reported only once

Re: linux-next: Tree for Mar 20 (vmcore)

2013-03-20 Thread Randy Dunlap
On 03/20/13 11:56, David Rientjes wrote: On Wed, 20 Mar 2013, Randy Dunlap wrote: on x86_64: fs/proc/vmcore.c: In function 'merge_note_headers_elf64': fs/proc/vmcore.c:349:22: error: 'VMCOREINFO_NOTE_NAME' undeclared (first use in this function) fs/proc/vmcore.c:349:22: note: each

Re: linux-next: Tree for Mar 20 (vmcore)

2013-03-20 Thread David Rientjes
On Wed, 20 Mar 2013, David Rientjes wrote: I don't think that's it, linux/kexec.h already gets included indirectly. The problem is that CONFIG_KEXEC isn't set so the definition in kexec.h is meaningless. This comes from vmcore: check NT_VMCORE_PAD as a mark indicating the end of ELF

Re: linux-next: Tree for Mar 20 (vmcore)

2013-03-20 Thread Stephen Rothwell
Hi, On Wed, 20 Mar 2013 17:10:30 -0700 (PDT) David Rientjes rient...@google.com wrote: On Wed, 20 Mar 2013, David Rientjes wrote: I don't think that's it, linux/kexec.h already gets included indirectly. The problem is that CONFIG_KEXEC isn't set so the definition in kexec.h is

Re: linux-next: Tree for Mar 20 (vmcore)

2013-03-20 Thread David Rientjes
On Thu, 21 Mar 2013, Stephen Rothwell wrote: What exactly are these patches so that I can remove them from my copy of the mmotm tree (assuming that Andrew does not get a new mmotm released in the next hour or so). [nacked]

Re: linux-next: Tree for Mar 20 (vmcore)

2013-03-20 Thread Stephen Rothwell
Hi David, On Wed, 20 Mar 2013 19:49:09 -0700 (PDT) David Rientjes rient...@google.com wrote: On Thu, 21 Mar 2013, Stephen Rothwell wrote: What exactly are these patches so that I can remove them from my copy of the mmotm tree (assuming that Andrew does not get a new mmotm released in