From: Sudeep Holla <sudeep.holla@arm.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
Basil Eljuse <Basil.Eljuse@arm.com>,
lkft-triage@lists.linaro.org,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
fntoth@gmail.com, Arnd Bergmann <arnd@arndb.de>,
Anders Roxell <anders.roxell@linaro.org>
Subject: Re: Re: [PATCH v2 3/3] driver core: Replace open-coded list_last_entry()
Date: Mon, 30 Mar 2020 14:16:46 +0100 [thread overview]
Message-ID: <20200330131646.GC20031@bogus> (raw)
In-Reply-To: <20200330104340.GO1922688@smile.fi.intel.com>
On Mon, Mar 30, 2020 at 01:43:40PM +0300, Andy Shevchenko wrote:
[...]
>
> How this warning related to the patch in the subject? Does revert of the patch
> gives you no warning? (I will be very surprised).
>
I did a quick check reverting the $subject patch and it doesn't remove
extra warning. Sorry for the noise, I assumed so hastily, I was wrong.
--
Regards,
Sudeep
next prev parent reply other threads:[~2020-03-30 13:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 12:20 [PATCH v2 1/3] driver core: Break infinite loop when deferred probe can't be satisfied Andy Shevchenko
2020-03-24 12:20 ` [PATCH v2 2/3] driver core: Read atomic counter once in driver_probe_done() Andy Shevchenko
2020-03-24 12:55 ` Rafael J. Wysocki
2020-03-24 12:20 ` [PATCH v2 3/3] driver core: Replace open-coded list_last_entry() Andy Shevchenko
2020-03-24 12:53 ` Rafael J. Wysocki
2020-03-27 17:56 ` Naresh Kamboju
2020-03-27 19:40 ` Robin Murphy
2020-03-30 10:13 ` Sudeep Holla
2020-03-30 10:43 ` Andy Shevchenko
2020-03-30 13:16 ` Sudeep Holla [this message]
2020-03-30 12:45 ` Robin Murphy
2020-03-30 13:11 ` Andy Shevchenko
2020-03-30 13:29 ` Robin Murphy
2020-03-30 20:02 ` John Stultz
2020-03-30 13:25 ` Sudeep Holla
2020-03-28 7:25 ` Greg Kroah-Hartman
2020-03-24 12:52 ` [PATCH v2 1/3] driver core: Break infinite loop when deferred probe can't be satisfied Rafael J. Wysocki
2020-03-24 13:39 ` Andy Shevchenko
2020-03-24 15:36 ` Rafael J. Wysocki
2020-03-24 15:47 ` Andy Shevchenko
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=20200330131646.GC20031@bogus \
--to=sudeep.holla@arm.com \
--cc=Basil.Eljuse@arm.com \
--cc=anders.roxell@linaro.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=fntoth@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=rafael@kernel.org \
--cc=robin.murphy@arm.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;
as well as URLs for NNTP newsgroup(s).