From: Sasha Levin <sashal@kernel.org>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Greg KH" <greg@kroah.com>,
stable-commits@vger.kernel.org,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
intel-gfx@lists.freedesktop.org,
"Jani Nikula" <jani.nikula@linux.intel.com>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Tvrtko Ursulin" <tvrtko.ursulin@linux.intel.com>,
"Oded Gabbay" <ogabbay@kernel.org>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Subject: Re: Re: Patch "drm: Fix color LUT rounding" has been added to the 6.7-stable tree
Date: Fri, 2 Feb 2024 14:38:57 -0500 [thread overview]
Message-ID: <Zb1E0YF0KwOTO8Vi@sashalap> (raw)
In-Reply-To: <4rfubhgx5ro6uyril7labgxoovuj26funttdts6bbcrbdfjxlj@mrwxtts657g2>
On Fri, Feb 02, 2024 at 11:35:33AM -0600, Lucas De Marchi wrote:
>On Fri, Feb 02, 2024 at 06:53:03PM +0200, Ville Syrjälä wrote:
>>On Thu, Feb 01, 2024 at 11:17:28AM -0800, Greg KH wrote:
>>>On Thu, Feb 01, 2024 at 08:35:24PM +0200, Ville Syrjälä wrote:
>>>> On Thu, Feb 01, 2024 at 10:16:48AM -0800, Greg KH wrote:
>>>> > On Thu, Feb 01, 2024 at 08:05:19PM +0200, Ville Syrjälä wrote:
>>>> > > On Thu, Feb 01, 2024 at 12:03:20PM -0500, Sasha Levin wrote:
>>>> > > > This is a note to let you know that I've just added the patch titled
>>>> > > >
>>>> > > > drm: Fix color LUT rounding
>>>> > > >
>>>> > > > to the 6.7-stable tree which can be found at:
>>>> > > > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>>>> > > >
>>>> > > > The filename of the patch is:
>>>> > > > drm-fix-color-lut-rounding.patch
>>>> > > > and it can be found in the queue-6.7 subdirectory.
>>>> > > >
>>>> > > > If you, or anyone else, feels it should not be added to the stable tree,
>>>> > > > please let <stable@vger.kernel.org> know about it.
>>>> > >
>>>> > > I guess I wasn't clear enough in the other mail...
>>>> > >
>>>> > > NAK for all of backports of this patch.
>>>> >
>>>> > Ok, but why? It seems that you are fixing a real issue here, right? If
>>>> > not, the changelog is not clear with that at all...
>>>> >
>>>> > I'll go drop it now, thanks.
>>>>
>>>> Because backporting it would require other backports that depend on
>>>> the rounding behaviour.
>>>>
>>>> Can I somehow fully opt out of these automagic backports?
>>>> If I want my stuff backported I'll ask for it.
>>>
>>>You can, just let me know what exact files should be ignored, or you can
>>>send a patch against this file:
>>> https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/ignore_list
>>
>>I think we should add at least i915 and xe there. cc: maintainers
>
>It does feel a little wild to decide a patch needs to be backported
>based on the commit title starting with "Fix", or whatever way was used
>here. We always relied on patches being backported based on a) having a
>Fixes: trailer and b) the commit pointed out in that trailer
>being present in that stable version. Or the others options shown
>in Documentation/process/stable-kernel-rules.rst
>
>Looking at the commit in question, c6fbb6bca10838485b820e8a26c23996f77ce580
>there's no such a trailer. Did I miss something from
>Documentation/process/stable-kernel-rules.rst?
Where did you see anything about the Fixes: trailer in the document
you've pointed to?
--
Thanks,
Sasha
next prev parent reply other threads:[~2024-02-02 19:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240201170320.69864-1-sashal@kernel.org>
[not found] ` <ZbvdXx7-GSUljUh1@intel.com>
[not found] ` <2024020119-user-aviation-b3c5@gregkh>
[not found] ` <ZbvkbJFs-hQ1wi4o@intel.com>
[not found] ` <2024020120-unclog-junction-8a5f@gregkh>
2024-02-02 16:53 ` Patch "drm: Fix color LUT rounding" has been added to the 6.7-stable tree Ville Syrjälä
2024-02-02 17:35 ` Lucas De Marchi
2024-02-02 19:38 ` Sasha Levin [this message]
2024-02-02 20:14 ` Lucas De Marchi
2024-02-02 21:15 ` Sasha Levin
2024-02-02 21:04 ` 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=Zb1E0YF0KwOTO8Vi@sashalap \
--to=sashal@kernel.org \
--cc=airlied@gmail.com \
--cc=greg@kroah.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=lucas.demarchi@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=ogabbay@kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=stable-commits@vger.kernel.org \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tvrtko.ursulin@linux.intel.com \
--cc=tzimmermann@suse.de \
--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