From: Fengguang Wu <lkp@intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Alexandre Courbot <gnurou@gmail.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
William Breathitt Gray <vilhelm.gray@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kbuild-all@01.org" <kbuild-all@01.org>
Subject: Re: [kbuild-all] [PATCH] gpio: fix platform_no_drv_owner.cocci warnings
Date: Fri, 16 Oct 2015 23:53:11 +0800 [thread overview]
Message-ID: <20151016155311.GA24534@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <20151016154723.GA23531@wfg-t540p.sh.intel.com>
On Fri, Oct 16, 2015 at 11:47:23PM +0800, Fengguang Wu wrote:
> On Fri, Oct 16, 2015 at 04:47:23PM +0200, Linus Walleij wrote:
> > On Wed, Oct 7, 2015 at 5:14 AM, kbuild test robot <lkp@intel.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@gmail.com>
> > > Signed-off-by: Fengguang Wu <fengguang.wu@intel.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.
>
> Hi Linus, the patch email does not start with "Re:", however it does contain
>
> In-Reply-To: <1444997709-57293-2-git-send-email-ck.hu@mediatek.com>
>
> So it should show up in the same thread as this email?
>
> [RFC 2/2] drm/bridge: Add I2C based driver for ps8640 bridge
Sorry it's not that email, but here is the mutt thread view in my mbox:
Oct 06 William Breathi (7.8K:0) [PATCH v4] gpio: Add GPIO support for the ACCES 104-IDIO-16
Oct 07 kbuild test rob (0.9K:0) |->[PATCH] gpio: fix platform_no_drv_owner.cocci warnings
Oct 16 Fengguang Wu (1.3K:0) | `->Re: [kbuild-all] [PATCH] gpio: fix platform_no_drv_owner.cocci warnings
Oct 07 kbuild test rob (0.7K:0) `->Re: [PATCH v4] gpio: Add GPIO support for the ACCES 104-IDIO-16
Thanks,
Fengguang
prev parent reply other threads:[~2015-10-16 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 3:14 [PATCH v4] gpio: Add GPIO support for the ACCES 104-IDIO-16 kbuild test robot
2015-10-07 2:40 ` William Breathitt Gray
2015-10-07 3:14 ` [PATCH] gpio: fix platform_no_drv_owner.cocci warnings kbuild test robot
2015-10-16 14:47 ` Linus Walleij
2015-10-16 15:47 ` [kbuild-all] " Fengguang Wu
2015-10-16 15:53 ` Fengguang Wu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151016155311.GA24534@wfg-t540p.sh.intel.com \
--to=lkp@intel.com \
--cc=gnurou@gmail.com \
--cc=kbuild-all@01.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vilhelm.gray@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®