From: Tyler Hicks <code@tyhicks.com>
To: gregkh@linuxfoundation.org, Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org
Subject: Process question about dropped patches
Date: Fri, 14 Oct 2022 15:55:03 -0500 [thread overview]
Message-ID: <20221014205503.3w2ge6srfpk6gtlt@sequoia> (raw)
Hey Greg and Sasha - I'm starting to think through how I can monitor for
dropped stable patches that touch certain file paths in order to help
out with backporting. I've come across a few examples where Greg's
automated emails point out that the patch couldn't be applied to a
certain series but then the patch shows up in a future -rc release
without anyone submitting a fixed backport to the list. An example:
FAILED email: https://lore.kernel.org/stable/1664091338227131@kroah.com/
-rc review email: https://lore.kernel.org/stable/20221003070722.143782710@linuxfoundation.org/
Is this just a case of one of you manually doing the backports (or
dependency resolution) yourselves or are folks directly sending you
backports?
This isn't a problem for me, BTW. I just want to make sure that I
understand the process. Thanks!
Tyler
next reply other threads:[~2022-10-14 20:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 20:55 Tyler Hicks [this message]
2022-10-15 11:24 ` Process question about dropped patches Sasha Levin
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=20221014205503.3w2ge6srfpk6gtlt@sequoia \
--to=code@tyhicks.com \
--cc=gregkh@linuxfoundation.org \
--cc=sashal@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