Prev: sound/pci/asihpi: Use kzalloc
Next: ramzswap: Eliminate stale data from compressed memory (v2 resend)
From: Stephen Rothwell on 17 May 2010 02:20 Hi Greg, After merging the usb tree, today's linux-next build (powerpc ppc44x_defconfig) produced this warning: drivers/usb/core/usb.c:596: warning: 'match_device' defined but not used Introduced by commit c8a3789b05e2ed43d8fd98934edbf66587cd3f96 ("USB: remove usb_find_device") which removed the last user of this function. -- Cheers, Stephen Rothwell sfr(a)canb.auug.org.au http://www.canb.auug.org.au/~sfr/
From: Greg KH on 17 May 2010 14:30 On Mon, May 17, 2010 at 04:16:03PM +1000, Stephen Rothwell wrote: > Hi Greg, > > After merging the usb tree, today's linux-next build (powerpc allyesconfig) > produced this warning: > > drivers/usb/host/xhci-ring.c: In function 'prepare_ring': > drivers/usb/host/xhci-ring.c:1729: warning: unused variable 'addr' > > Introduced by commit a2fbb0e4784f6d1b3be0779918e84dd3c0c73f04 ("USB: > xhci: Transfer ring link TRB activation change"). Thanks, I'll go fix this up. greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Greg KH on 17 May 2010 14:30
On Mon, May 17, 2010 at 04:09:58PM +1000, Stephen Rothwell wrote: > Hi Greg, > > After merging the usb tree, today's linux-next build (powerpc > ppc44x_defconfig) produced this warning: > > drivers/usb/core/usb.c:596: warning: 'match_device' defined but not used > > Introduced by commit c8a3789b05e2ed43d8fd98934edbf66587cd3f96 ("USB: > remove usb_find_device") which removed the last user of this function. Thanks, Ming just sent me a patch to resolve this, I'll go apply it now. greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |