From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Sasha Levin <sashal@kernel.org>,
"kernelci.org bot" <bot@kernelci.org>,
tomeu.vizoso@collabora.com, guillaume.tucker@collabora.com,
Niklas Cassel <niklas.cassel@linaro.org>,
broonie@kernel.org, khilman@baylibre.com, mgalka@collabora.com,
enric.balletbo@collabora.com, linux-pm@vger.kernel.org,
Stephen Boyd <sboyd@codeaurora.org>,
linux-kernel@vger.kernel.org, Nishanth Menon <nm@ti.com>,
Len Brown <len.brown@intel.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Pavel Machek <pavel@ucw.cz>, Viresh Kumar <vireshk@kernel.org>
Subject: Re: stable/linux-4.14.y bisection: boot on odroid-x2
Date: Thu, 21 Nov 2019 07:58:21 +0100 [thread overview]
Message-ID: <20191121065821.GA344102@kroah.com> (raw)
In-Reply-To: <20191121060811.mvzzh4zlfzlubzlv@vireshk-i7>
On Thu, Nov 21, 2019 at 11:38:11AM +0530, Viresh Kumar wrote:
> On 20-11-19, 18:52, kernelci.org bot wrote:
> > commit 714ab224a8db6e8255c61a42613de9349ceb0bba
> > Author: Viresh Kumar <viresh.kumar@linaro.org>
> > Date: Fri Aug 3 07:05:21 2018 +0530
> >
> > OPP: Protect dev_list with opp_table lock
> >
> > [ Upstream commit 3d2556992a878a2210d3be498416aee39e0c32aa ]
> >
> > The dev_list needs to be protected with a lock, else we may have
> > simultaneous access (addition/removal) to it and that would be racy.
> > Extend scope of the opp_table lock to protect dev_list as well.
> >
> > Tested-by: Niklas Cassel <niklas.cassel@linaro.org>
> > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> > Signed-off-by: Sasha Levin <sashal@kernel.org>
>
> @Sasha: Please drop this patch for now.
Drop it from 4.14 and 4.19?
thanks,
greg k-h
next prev parent reply other threads:[~2019-11-21 6:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 2:52 stable/linux-4.14.y bisection: boot on odroid-x2 kernelci.org bot
2019-11-21 6:08 ` Viresh Kumar
2019-11-21 6:58 ` Greg Kroah-Hartman [this message]
2019-11-21 8:55 ` Viresh Kumar
2019-11-21 13:52 ` Greg Kroah-Hartman
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=20191121065821.GA344102@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bot@kernelci.org \
--cc=broonie@kernel.org \
--cc=enric.balletbo@collabora.com \
--cc=guillaume.tucker@collabora.com \
--cc=khilman@baylibre.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mgalka@collabora.com \
--cc=niklas.cassel@linaro.org \
--cc=nm@ti.com \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--cc=sashal@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=tomeu.vizoso@collabora.com \
--cc=viresh.kumar@linaro.org \
--cc=vireshk@kernel.org \
/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.