On Sat, Mar 18, 2017 at 10:40:06PM -0700, Michael Zoran wrote: > On Sun, 2017-03-19 at 13:27 +0800, kbuild test robot wrote: > > Hi Michael, > > > > [auto build test WARNING on staging/staging-testing] > > [also build test WARNING on next-20170310] > > [cannot apply to linux-rpi/for-rpi-next v4.11-rc2] > > [if your patch is applied to the wrong git tree, please drop us a > > note to help improve the system] > > > > url: https://github.com/0day-ci/linux/commits/Michael-Zoran/stagin > > g-bcm2835-firmware-gpio-Initial-staging-commit/20170319-111114 > > > > > > coccinelle warnings: (new ones prefixed by >>) > > > > > > drivers/staging/vc04_services/bcm2835-firmware-gpio/gpio-bcm- > > > > exp.c:271:3-8: No need to set .owner here. The core will do it. > > > > > Please review and possibly fold the followup patch. > > > > --- > > 0-DAY kernel test infrastructure Open Source > > Technology Center > > https://lists.01.org/pipermail/kbuild-all ; Intel > > Corporation > > OK, Some I'm completely confused here. Has this patch been applied, > and through which tree has it been applied to? > > I think I need to send a V2. So who should I be sending V2 to? kbuild grabs patches off the mailing list and automatically tests them. They haven't been applied. Just resend a normal v2 series. regards, dan carpenter _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
