All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Yenchia Chen <yenchia.chen@mediatek.com>
Cc: stable@vger.kernel.org, "Rafael J. Wysocki" <rafael@kernel.org>,
	Pavel Machek <pavel@ucw.cz>, Len Brown <len.brown@intel.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 5.15 0/1] pm, restore async device resume optimization
Date: Mon, 2 Sep 2024 08:01:10 +0200	[thread overview]
Message-ID: <2024090220-uncaring-pretext-4391@gregkh> (raw)
In-Reply-To: <20240902031047.9865-1-yenchia.chen@mediatek.com>

On Mon, Sep 02, 2024 at 11:10:44AM +0800, Yenchia Chen wrote:
> From: "yenchia.chen" <yenchia.chen@mediatek.com>
> 
> We have met a deadlock issue on our device when resuming.
> After applying this patch which is picked from mainline, issue solved.
> We'd like to backport to 5.15.y and could you help to review? thanks.
> 
> [ Upstream commit 3e999770ac1c7c31a70685dd5b88e89473509e9c ]

For obvious reasons (and as per the documentation), we can't take
commits that are not also in all newer kernel releases, otherwise you
would have a regression if you moved to a newer kernel, right?

Please submit a series for all affected releases if you wish for a patch
to be applied to the trees.

thanks,

greg k-h


  parent reply	other threads:[~2024-09-02  6:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-02  3:10 [PATCH 5.15 0/1] pm, restore async device resume optimization Yenchia Chen
2024-09-02  3:10 ` [PATCH 5.15 1/1] PM: sleep: Restore asynchronous " Yenchia Chen
2024-09-02  3:12   ` kernel test robot
2024-09-02  6:00   ` Greg Kroah-Hartman
2024-09-02  9:04     ` [PATCH 5.15 v2] " Yenchia Chen
2024-09-02  6:01 ` Greg Kroah-Hartman [this message]
2024-09-02 12:37   ` [PATCH 5.15 0/1] pm, restore async " Yenchia Chen

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=2024090220-uncaring-pretext-4391@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=len.brown@intel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=matthias.bgg@gmail.com \
    --cc=pavel@ucw.cz \
    --cc=rafael@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=yenchia.chen@mediatek.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.