| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <CACRpkdYfX9LqO8jjdhsp-MxJEqwHRudpjMqZhyvLbgxeGs9SSQ@mail.gmail.com> Date: Fri, 16 Oct 2015 16:47:23 +0200 From: Linus Walleij <linus.walleij@...aro.org> To: kbuild test robot <lkp@...el.com> Cc: William Breathitt Gray <vilhelm.gray@...il.com>, "kbuild-all@...org" <kbuild-all@...org>, Alexandre Courbot <gnurou@...il.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org> Subject: Re: [PATCH] gpio: fix platform_no_drv_owner.cocci warnings On Wed, Oct 7, 2015 at 5:14 AM, kbuild test robot <lkp@...el.com> wrote: > drivers/gpio/gpio-104-idio-16.c:151:3-8: No need to set .owner here. The core will do it. > > Remove .owner field if calls are used which set it automatically > > Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci > > CC: William Breathitt Gray <vilhelm.gray@...il.com> > Signed-off-by: Fengguang Wu <fengguang.wu@...el.com> This is confusing, I mix up the mails coming from my pushed git branches with this new stuff that is obviously checking patches I haven't even applied. It's better if these kbuild fixes are sent as Re: to the mail ID of the patch so it appears in the same thread as the offending patch on the mailing list. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists