From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Aditya Garg <gargaditya08@live.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
Jiri Slaby <jirislaby@kernel.org>
Subject: Re: [BACKPORT] HID: apple: remove unused members from struct apple_sc_backlight
Date: Mon, 1 Jul 2024 16:33:14 +0200 [thread overview]
Message-ID: <2024070140-daydream-peddling-986e@gregkh> (raw)
In-Reply-To: <6919952F-1AF6-4D16-BE61-686C5D8F5A87@live.com>
On Mon, Jul 01, 2024 at 02:18:55PM +0000, Aditya Garg wrote:
> Commit f740106aedd3 (HID: apple: remove unused members from struct apple_sc_backlight) in Linus’ tree imo should be back ported to:
>
> 1. Linux 6.6
> 2. Linux 6.1
>
> since there hasn't been any change to the backlight code in the driver ever since it has been upstreamed. So it should be safe to remove the unused members from struct apple_sc_backlight
Why? What bug does this fix?
Have you read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for what is relevant for stable kernel trees?
thanks,
greg k-h
prev parent reply other threads:[~2024-07-01 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 14:18 [BACKPORT] HID: apple: remove unused members from struct apple_sc_backlight Aditya Garg
2024-07-01 14:33 ` gregkh [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=2024070140-daydream-peddling-986e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=gargaditya08@live.com \
--cc=jirislaby@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