On Wed, Mar 21, 2007 at 03:59:53PM -0700, Andrew Morton wrote: > On Wed, 21 Mar 2007 22:17:48 +0000 > Russell King <[EMAIL PROTECTED]> wrote: > > > On Wed, Mar 21, 2007 at 03:11:00PM -0700, [EMAIL PROTECTED] wrote: > > > ------------------------------------------------------ > > > Subject: move die notifier handling to common code > > > From: Christoph Hellwig <[EMAIL PROTECTED]> > > > > > > This patch moves the die notifier handling to common code. Previous > > > various architectures had exactly the same code for it. Note that the new > > > code is compiled unconditionally, this should be understood as an appel to > > > the other architecture maintainer to implement support for it aswell (aka > > > sprinkling a notify_die or two in the proper place) > > > > > > arm had a notifiy_die that did something totally different, I renamed it > > > to > > > arm_notify_die as part of the patch and made it static to the file it's > > > declared and used at. avr32 used to pass slightly less information > > > through > > > this interface and I brought it into line with the other architectures. > > > > > > Signed-off-by: Christoph Hellwig <[EMAIL PROTECTED]> > > > Cc: <[email protected]> > > > Signed-off-by: Andrew Morton <[EMAIL PROTECTED]> > > > > NAK. This will, as seems to be the current favourite past time, break > > ARM. A simple grep command will show why; I leave it as an exercise for > > those to run this command to discover the details. > > > > $ grep notify_die arch/arm -r > > There seems to be one missed conversion in > arch/arm/mm/fault.c:do_DataAbort(). If that's not what you mean then > perhaps you can give us another hint.
That and the blatent removal of the prototype from asm-arm/system.h along with the non-static declaration in arch/arm/kernel/traps.c should've been sufficient clue that it might be used somewhere else. I note that it became static in hch's patch... It seems that breaking ARM builds is all the rage; they've broken three times during this cycle due to peoples dumb untested patches, and with the restrictions Linus placed on my merging it's painful to keep resolving these issues one week or so after they happen. Thankfully, I've caught this one prior to it hitting mainline. Folk *need* to spend more time testing their work before submitting it upstream. Merely building the ARM defconfig would've found this error. -- Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: - To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
