public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Dave Airlie <airlied@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>,
	stable@vger.kernel.org, ashutosh.dixit@intel.com,
	dri-devel@lists.freedesktop.org
Subject: Re: AAARRRGGGHHH!!!! (was Re: [PATCH 6.12.y] xe/oa: Fix query mode of operation for OAR/OAC)
Date: Mon, 13 Jan 2025 16:48:17 -0500	[thread overview]
Message-ID: <Z4WKIbVzo8d-nln3@lappy> (raw)
In-Reply-To: <CAPM=9tx1cFzhaZNz=gQOmP9Q0KEK5fMKZYSc-P0xA_f2sxoZ9w@mail.gmail.com>

On Mon, Jan 13, 2025 at 10:44:41AM +1000, Dave Airlie wrote:
>Pretty sure we've explained how a few times now, not sure we can do much more.
>
>If you see a commit with a cherry-pick link in it and don't have any
>sight on that commit in Linus's tree, ignore the cherry-pick link in
>it, assume it's a future placeholder for that commit id. You could if
>you wanted to store that info somewhere, but there shouldn't be a
>need.
>
>When the initial commit enters during the next merge window, you look
>for that subject or commit id in the stable tree already, if it
>exists, dump the latest Linus patch on the floor, it's already in
>stable your job is done.

We can't rely too heavily on the subject line. Consider the following two
very different commits that have the same subject line:

	3119668c0e0a ("drm/amd/display: avoid disable otg when dig was disabled")
	218784049f4b ("drm/amd/display: avoid disable otg when dig was disabled")

Now, if a new commit lands and it has the following "Fixes:" tag:

	Fixes: abcdef12345 ("drm/amd/display: avoid disable otg when dig was disabled")

Does it refer to one of the older commits? Or a new commit that will
show up during the merge window?

Or... What happens if a new commit with the very same subject line shows
up, and it has a cherry-pick link that points to a completely different
commit that is not in the tree yet? :)

But just in general, there are so many odd combinations of commits where
trying to follow the suggestion you've made will just break...

Something like these two identical commits which are not tagged for stable:

	21afc872fbc2 ("drm/amd/display: Add monitor patch for specific eDP")
	3d71a8726e05 ("drm/amd/display: Add monitor patch for specific eDP")

And the following two identical ones which are tagged for stable:

	b7cdccc6a849 ("drm/amd/display: Add monitor patch for specific eDP")
	04a59c547575 ("drm/amd/display: Add monitor patch for specific eDP")

-- 
Thanks,
Sasha

  parent reply	other threads:[~2025-01-13 21:48 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-06 10:06 FAILED: patch "[PATCH] xe/oa: Fix query mode of operation for OAR/OAC" failed to apply to 6.12-stable tree gregkh
2025-01-10 20:53 ` [PATCH 6.12.y] xe/oa: Fix query mode of operation for OAR/OAC Umesh Nerlige Ramappa
2025-01-11 19:04   ` Sasha Levin
2025-01-12 11:28   ` Greg KH
2025-01-12 11:39   ` AAARRRGGGHHH!!!! (was Re: [PATCH 6.12.y] xe/oa: Fix query mode of operation for OAR/OAC) Greg KH
2025-01-12 19:51     ` Dave Airlie
2025-01-12 20:01       ` Dave Airlie
2025-01-12 21:09         ` Greg KH
2025-01-13  0:44           ` Dave Airlie
2025-01-13  8:05             ` Greg KH
2025-01-14  1:01               ` Dave Airlie
2025-01-14 15:03                 ` Simona Vetter
2025-01-14 15:51                   ` Sasha Levin
2025-01-14 16:11                     ` Alex Deucher
2025-01-15  9:20                       ` Greg KH
2025-01-14 17:31                     ` Simona Vetter
2025-01-15  9:07                       ` Simona Vetter
2025-01-15  9:38                         ` Greg KH
2025-01-15 11:15                           ` Simona Vetter
2025-01-15 17:18                             ` Sasha Levin
2025-01-15 19:02                               ` Simona Vetter
2025-01-16  9:48                                 ` Simona Vetter
2025-01-16 13:52                                   ` Greg KH
2025-01-16 14:30                                     ` Simona Vetter
2025-01-13 21:48             ` Sasha Levin [this message]
2025-01-14 16:16               ` Simona Vetter
2025-01-14 15:59             ` Simona Vetter
2025-01-12 21:06       ` Greg KH
2025-01-17 11:01         ` Uwe Kleine-König
2025-01-17 11:25           ` Greg KH
2025-01-14  1:12     ` Dave Airlie
2025-01-14  9:22       ` Jani Nikula
2025-01-15  9:11         ` Greg KH
2025-01-15  9:30           ` Simona Vetter

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=Z4WKIbVzo8d-nln3@lappy \
    --to=sashal@kernel.org \
    --cc=airlied@gmail.com \
    --cc=ashutosh.dixit@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=stable@vger.kernel.org \
    --cc=umesh.nerlige.ramappa@intel.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