From: Sasha Levin <sashal@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Dmitry Osipenko <digetx@gmail.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
linux-spi@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 5.14 133/252] spi: tegra20-slink: Improve runtime PM usage
Date: Mon, 13 Sep 2021 13:14:49 -0400 [thread overview]
Message-ID: <YT+HCdNjfQxQayYH@sashalap> (raw)
In-Reply-To: <20210909130450.GB5176@sirena.org.uk>
On Thu, Sep 09, 2021 at 02:04:50PM +0100, Mark Brown wrote:
>On Thu, Sep 09, 2021 at 03:45:45PM +0300, Dmitry Osipenko wrote:
>> 09.09.2021 15:37, Mark Brown пишет:
>
>> > This feels new featureish to me - it'll give you runtime PM where
>> > previously there was none.
>
>> Apparently all patches which have a word 'fix' in commit message are
>> auto-selected. I agree that it's better not to port this patch.
>
>Yeah, it's a fairly common source of false positives :/
And some of that falls on me: if it's obvious that the "fix" isn't a
real fix, I won't take it. In cases like this it's not clear to me
whether it's purely a better behaviour, or whether the devices staying
on/off/etc causes an actual problem.
--
Thanks,
Sasha
next prev parent reply other threads:[~2021-09-13 17:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210909114106.141462-1-sashal@kernel.org>
2021-09-09 11:37 ` [PATCH AUTOSEL 5.14 058/252] spi: imx: fix ERR009165 Sasha Levin
2021-09-09 16:42 ` Lucas Stach
2021-09-09 16:48 ` Fabio Estevam
2021-09-10 3:30 ` Robin Gong
2021-09-13 16:47 ` Sasha Levin
2021-09-09 11:37 ` [PATCH AUTOSEL 5.14 059/252] spi: imx: remove ERR009165 workaround on i.mx6ul Sasha Levin
2021-09-09 11:39 ` [PATCH AUTOSEL 5.14 133/252] spi: tegra20-slink: Improve runtime PM usage Sasha Levin
2021-09-09 12:37 ` Mark Brown
2021-09-09 12:45 ` Dmitry Osipenko
2021-09-09 13:04 ` Mark Brown
2021-09-13 17:14 ` Sasha Levin [this message]
2021-09-14 13:44 ` Dmitry Osipenko
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=YT+HCdNjfQxQayYH@sashalap \
--to=sashal@kernel.org \
--cc=broonie@kernel.org \
--cc=digetx@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox