Hi Greg, I believe I understand the cause of the problem and would like to submit a patch to fix it. However, I am unclear on what the starting point is given that the final patch was reverted from linux-next. Do I assume that patch will be reapplied before the applying the new patch or should I provide another patch to reapply the reverted patch? Is it acceptable to submit patches generated against the head of linux-next? Before submitting the patch, I would like to test that the patch really does fix the issue found by Stephen. Since it doesn't occur when building for x32 or x64 then I need to setup a PowerPC cross-compile tool chain. Do you have any suggestions as to where I can pull a prebuilt tool chain or do I need to build directly from the GNU sources. Many thanks for your help Kind regards Chris Kelly -----Original Message----- From: Greg KH [mailto:gregkh@xxxxxxxxxxxxxxxxxxx] Sent: 27 February 2012 9:17 PM To: Stephen Rothwell Cc: linux-next@xxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; Chris Kelly Subject: Re: linux-next: build failure after merge of the final tree (staging tree related) On Mon, Feb 27, 2012 at 06:13:03PM +1100, Stephen Rothwell wrote: > Hi all, > > After merging the final tree, today's linux-next build > (powerpc_allyesconfig) failed like this: > > drivers/staging/ozwpan/ozcdev.c: In function 'oz_cdev_ioctl': > drivers/staging/ozwpan/ozcdev.c:284:7: error: case label does not reduce to an integer constant > > Caused by commit 23af8c2a088f ("staging: ozwpan: Added character device > support") from the staging tree. > > I reverted commit b0406db5b3e4 ("staging: ozwpan: Plumbed in Kconfig and > Kbuild") for today. Thanks, Chris, care to fix this up and send me a patch? greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
