From: Vignesh Raghavendra <vigneshr@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Dinghao Liu <dinghao.liu@zju.edu.cn>, <kjlu@umn.edu>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
<linux-omap@vger.kernel.org>, <linux-i2c@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] i2c: omap: Fix rumtime PM imbalance on error
Date: Wed, 7 Apr 2021 13:15:32 +0530 [thread overview]
Message-ID: <30ed0224-fba3-75c6-c4aa-e2d0724c291b@ti.com> (raw)
In-Reply-To: <YG1Qt56QSjyFqZxd@atomide.com>
Hi,
On 4/7/21 11:57 AM, Tony Lindgren wrote:
> * Vignesh Raghavendra <vigneshr@ti.com> [210407 06:20]:
>> Do we need a Fixes: tag to enable stable backports?
>
> Well pm_runtime_resume_and_get() was introduced quite recently, and
> we already handle the error and bail out. And likely after an error
> not much works anyways :) So it might be better to add just a stable
> tag v5.10 and later as further backports are not likely needed.
>
Agree this is not a critical patch for backport. But I do know that
pm_runtime_resume_and_get() is backported to v5.4 stable kernel at least
[1]. So stable tag with v5.4 perhaps would probably help tools looking
for patches to backport.
[1] https://lkml.org/lkml/2020/12/28/588
> Naturally nothing stopping doing separate backports if really needed
> though.
>
> Regards,
>
> Tony
>
Regards
Vignesh
next prev parent reply other threads:[~2021-04-07 7:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 3:30 [PATCH] i2c: omap: Fix rumtime PM imbalance on error Dinghao Liu
2021-04-07 6:10 ` Tony Lindgren
2021-04-07 6:19 ` Vignesh Raghavendra
2021-04-07 6:27 ` Tony Lindgren
2021-04-07 7:45 ` Vignesh Raghavendra [this message]
2021-04-07 9:59 ` Tony Lindgren
2021-04-14 7:54 ` Wolfram Sang
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=30ed0224-fba3-75c6-c4aa-e2d0724c291b@ti.com \
--to=vigneshr@ti.com \
--cc=aaro.koskinen@iki.fi \
--cc=dinghao.liu@zju.edu.cn \
--cc=kjlu@umn.edu \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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).