From: Rong Chen <rong.a.chen@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
kbuild test robot <lkp@intel.com>
Cc: Colin King <colin.king@canonical.com>,
kbuild-all@lists.01.org, Sekhar Nori <nsekhar@ti.com>,
Roger Quadros <rogerq@ti.com>,
Felipe Balbi <felipe.balbi@linux.intel.com>,
Pawel Laszczak <pawell@cadence.com>,
linux-usb@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [kbuild-all] Re: [RFC PATCH] usb: cdns3: cdns3_clear_register_bit() can be static
Date: Fri, 27 Mar 2020 08:34:52 +0800 [thread overview]
Message-ID: <571960b6-5ed7-2106-7091-3ea83c31051a@intel.com> (raw)
In-Reply-To: <20200326130418.GA1295433@kroah.com>
On 3/26/20 9:04 PM, Greg Kroah-Hartman wrote:
> On Thu, Mar 26, 2020 at 08:28:58PM +0800, kbuild test robot wrote:
>> Fixes: 87db1192dc33 ("usb: cdns3: make signed 1 bit bitfields unsigned")
> This original patch did not "cause" this problem, it's just that you for
> some reason ran sparse for the first time on the file.
>
> So I can't take this as-is, can you remove this line and resend?
Hi Greg,
Sorry for the inconvenience, the patch was generated by the bot,
we'll check and resend it.
Best Regards,
Rong Chen
>
> thanks,
>
> greg k-h
> _______________________________________________
> kbuild-all mailing list -- kbuild-all@lists.01.org
> To unsubscribe send an email to kbuild-all-leave@lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: Rong Chen <rong.a.chen@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
kbuild test robot <lkp@intel.com>
Cc: Colin King <colin.king@canonical.com>,
kbuild-all@lists.01.org, Sekhar Nori <nsekhar@ti.com>,
Roger Quadros <rogerq@ti.com>,
Felipe Balbi <felipe.balbi@linux.intel.com>,
Pawel Laszczak <pawell@cadence.com>,
linux-usb@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [kbuild-all] Re: [RFC PATCH] usb: cdns3: cdns3_clear_register_bit() can be static
Date: Fri, 27 Mar 2020 00:34:52 +0000 [thread overview]
Message-ID: <571960b6-5ed7-2106-7091-3ea83c31051a@intel.com> (raw)
In-Reply-To: <20200326130418.GA1295433@kroah.com>
On 3/26/20 9:04 PM, Greg Kroah-Hartman wrote:
> On Thu, Mar 26, 2020 at 08:28:58PM +0800, kbuild test robot wrote:
>> Fixes: 87db1192dc33 ("usb: cdns3: make signed 1 bit bitfields unsigned")
> This original patch did not "cause" this problem, it's just that you for
> some reason ran sparse for the first time on the file.
>
> So I can't take this as-is, can you remove this line and resend?
Hi Greg,
Sorry for the inconvenience, the patch was generated by the bot,
we'll check and resend it.
Best Regards,
Rong Chen
>
> thanks,
>
> greg k-h
> _______________________________________________
> kbuild-all mailing list -- kbuild-all@lists.01.org
> To unsubscribe send an email to kbuild-all-leave@lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: Rong Chen <rong.a.chen@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH] usb: cdns3: cdns3_clear_register_bit() can be static
Date: Fri, 27 Mar 2020 08:34:52 +0800 [thread overview]
Message-ID: <571960b6-5ed7-2106-7091-3ea83c31051a@intel.com> (raw)
In-Reply-To: <20200326130418.GA1295433@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 744 bytes --]
On 3/26/20 9:04 PM, Greg Kroah-Hartman wrote:
> On Thu, Mar 26, 2020 at 08:28:58PM +0800, kbuild test robot wrote:
>> Fixes: 87db1192dc33 ("usb: cdns3: make signed 1 bit bitfields unsigned")
> This original patch did not "cause" this problem, it's just that you for
> some reason ran sparse for the first time on the file.
>
> So I can't take this as-is, can you remove this line and resend?
Hi Greg,
Sorry for the inconvenience, the patch was generated by the bot,
we'll check and resend it.
Best Regards,
Rong Chen
>
> thanks,
>
> greg k-h
> _______________________________________________
> kbuild-all mailing list -- kbuild-all(a)lists.01.org
> To unsubscribe send an email to kbuild-all-leave(a)lists.01.org
next prev parent reply other threads:[~2020-03-27 0:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 12:50 [PATCH] usb: cdns3: make signed 1 bit bitfields unsigned Colin King
2020-03-26 11:46 ` Peter Chen
2020-03-26 12:28 ` kbuild test robot
2020-03-26 12:28 ` kbuild test robot
2020-03-26 12:28 ` kbuild test robot
2020-03-26 12:28 ` [RFC PATCH] usb: cdns3: cdns3_clear_register_bit() can be static kbuild test robot
2020-03-26 12:28 ` kbuild test robot
2020-03-26 12:28 ` kbuild test robot
2020-03-26 13:04 ` Greg Kroah-Hartman
2020-03-26 13:04 ` Greg Kroah-Hartman
2020-03-26 13:04 ` Greg Kroah-Hartman
2020-03-27 0:34 ` Rong Chen [this message]
2020-03-27 0:34 ` Rong Chen
2020-03-27 0:34 ` [kbuild-all] " Rong Chen
2020-03-27 6:42 ` Greg Kroah-Hartman
2020-03-27 6:42 ` Greg Kroah-Hartman
2020-03-27 6:42 ` [kbuild-all] " Greg Kroah-Hartman
2020-03-27 6:53 ` Rong Chen
2020-03-27 6:53 ` Rong Chen
2020-03-27 6:53 ` [kbuild-all] " Rong Chen
2020-04-02 1:33 ` Rong Chen
2020-04-02 1:33 ` Rong Chen
2020-04-02 1:33 ` [kbuild-all] " Rong Chen
2020-03-27 1:12 ` [kbuild-all] [RFC PATCH v2] " kbuild test robot
2020-03-27 1:12 ` kbuild test robot
2020-03-27 1:12 ` [kbuild-all] " kbuild test robot
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=571960b6-5ed7-2106-7091-3ea83c31051a@intel.com \
--to=rong.a.chen@intel.com \
--cc=colin.king@canonical.com \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@lists.01.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lkp@intel.com \
--cc=nsekhar@ti.com \
--cc=pawell@cadence.com \
--cc=rogerq@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.