From: Greg KH <gregkh@linuxfoundation.org>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: andi.shyti@kernel.org, andi.shyti@linux.intel.com,
matthew.auld@intel.com, thomas.hellstrom@linux.intel.com,
ville.syrjala@linux.intel.com, sashal@kernel.org,
stable@vger.kernel.org, stable-commits@vger.kernel.org
Subject: Re: Patch "drm/i915/gem: Allow EXEC_CAPTURE on recoverable contexts on DG1" has been added to the 6.1-stable tree
Date: Wed, 2 Jul 2025 09:38:28 +0200 [thread overview]
Message-ID: <2025070249-blade-robotics-0bca@gregkh> (raw)
In-Reply-To: <175136652541.22602.12580210971758725103@jlahtine-mobl>
On Tue, Jul 01, 2025 at 01:42:05PM +0300, Joonas Lahtinen wrote:
> Hi Greg,
>
> Please do note that there is a revert for this patch that was part of
> the same pull request. That needs to be picked in too in case you are
> picking the original patch.
>
> I already got the automated mails from Sasha that both the original commit
> and revert were already picked into 6.1, 6.6 and 6.12 trees. Are now in
> a perpetual machinery induced loop where the original commit and revert will
> be picked in alternating fashion to the stable trees? [1]
Yes.
> Regards, Joonas
>
> [1] Originally, I was under the assumption stable machinery would
> automatically skip over patches that have later been reverted, but
> that doesn't seem to be the case?
Nope, if that were to happen then we would be adding it back over time
as we would go "hey, we missed this one!" all the time. Adding the
commit and revert is best.
thanks
greg k-h
prev parent reply other threads:[~2025-07-02 7:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2025063043-down-countable-2999@gregkh>
2025-07-01 10:42 ` Patch "drm/i915/gem: Allow EXEC_CAPTURE on recoverable contexts on DG1" has been added to the 6.1-stable tree Joonas Lahtinen
2025-07-02 7:38 ` Greg KH [this message]
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=2025070249-blade-robotics-0bca@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andi.shyti@kernel.org \
--cc=andi.shyti@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=matthew.auld@intel.com \
--cc=sashal@kernel.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=thomas.hellstrom@linux.intel.com \
--cc=ville.syrjala@linux.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