From: Greg KH <gregkh@linuxfoundation.org>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Imre Deak <imre.deak@intel.com>,
stable@vger.kernel.org, intel-gfx@lists.freedesktop.org,
Jani Nikula <jani.nikula@intel.com>
Subject: Re: v6.8 stable backport request for drm/i915
Date: Fri, 5 Apr 2024 06:29:47 +0200 [thread overview]
Message-ID: <2024040536-creature-starlet-9967@gregkh> (raw)
In-Reply-To: <Zg8aye1ee7T4dNJD@intel.com>
On Thu, Apr 04, 2024 at 05:25:29PM -0400, Rodrigo Vivi wrote:
> On Thu, Apr 04, 2024 at 04:53:07PM +0300, Imre Deak wrote:
> > On Thu, Apr 04, 2024 at 04:29:04PM +0300, Imre Deak wrote:
> > > Stable team, please backport the following upstream commit to 6.8:
> > >
> > > commit 7a51a2aa2384 ("drm/i915/dp: Fix DSC state HW readout for SST connectors")
> >
> > Just noticed that the above commit is not yet upstream, still only
> > queued in drm-intel-next. I presumed patches will be cherry-picked from
> > drm-intel-next to drm-intel-fixes based on the Fixes: tag, so I only
> > pushed the above patch to drm-intel-next; maybe the cherry picking
> > doesn't (always) happen automatically.
>
> This patch was cherry-picked this week and sent with the drm-intel-fixes
> pull request targeting v6.9-rc3
>
> Since it has the proper 'Fixes:' tag, it will likely get propagated to
> the stable branches 'automagically' in some near future.
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
prev parent reply other threads:[~2024-04-05 4:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 13:29 v6.8 stable backport request for drm/i915 Imre Deak
2024-04-04 13:53 ` Imre Deak
2024-04-04 21:25 ` Rodrigo Vivi
2024-04-05 4:29 ` 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=2024040536-creature-starlet-9967@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=rodrigo.vivi@intel.com \
--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