From: Brian Norris <briannorris@chromium.org>
To: gregkh@linuxfoundation.org
Cc: linux@roeck-us.net, stable@vger.kernel.org, ulf.hansson@linaro.org
Subject: Re: FAILED: patch "[PATCH] mmc: core: Terminate infinite loop in SD-UHS voltage switch" failed to apply to 5.19-stable tree
Date: Thu, 6 Oct 2022 12:10:42 -0700 [thread overview]
Message-ID: <Yz8oMnK1WHrUUvtf@google.com> (raw)
In-Reply-To: <16647043801297@kroah.com>
On Sun, Oct 02, 2022 at 11:53:00AM +0200, Greg Kroah-Hartman wrote:
>
> The patch below does not apply to the 5.19-stable tree.
> If someone wants it applied there, or to any other stable or longterm
> tree, then please email the backport, including the original git commit
> id to <stable@vger.kernel.org>.
>
> Possible dependencies:
>
> e9233917a7e5 ("mmc: core: Terminate infinite loop in SD-UHS voltage switch")
> e42726646082 ("mmc: core: Replace with already defined values for readability")
I think it would be most readable and least error prone to just backport
commit e42726646082 (it's trivial) along with $subject. I've confirmed
that together, these two patches apply cleanly to 4.14.y..5.19.y, and
the appropriate definitions are available.
4.9.y has some other conflicts, due to missing this:
09247e110b2e mmc: core: Allow UHS-I voltage switch for SDSC cards if supported
I'd personaly just skip $subject for 4.9.y too, although I could be
convinced to rewrite and submit a backport if someone feels strongly.
I'll assume Greg can pick the quoted two commits up (that more or less
fits Documentation/stable_kernel_rules.txt option 2), but I can submit a
proper patchset if needed.
Brian
next prev parent reply other threads:[~2022-10-06 19:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-02 9:53 FAILED: patch "[PATCH] mmc: core: Terminate infinite loop in SD-UHS voltage switch" failed to apply to 5.19-stable tree gregkh
2022-10-06 19:10 ` Brian Norris [this message]
2022-10-07 7:35 ` Greg KH
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=Yz8oMnK1WHrUUvtf@google.com \
--to=briannorris@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux@roeck-us.net \
--cc=stable@vger.kernel.org \
--cc=ulf.hansson@linaro.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