linux-kernel - Re: [PATCH linux dev-6.6] A backport request for SY24655 driver in INA2XX driver for Linux kernel 6.6.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <9f0447151e6574d74e7fa9cbbb50d8e970059273.camel@codeconstruct.com.au>
Date: Fri, 07 Feb 2025 10:18:29 +1030
From: Andrew Jeffery <andrew@...econstruct.com.au>
To: Rush Chen <rush_chen@...ynn.com>, openbmc@...ts.ozlabs.org,
 andrew@...id.au,  Guenter Roeck <linux@...ck-us.net>, Jean Delvare
 <jdelvare@...e.com>, Jonathan Corbet <corbet@....net>
Cc: linux-hwmon@...r.kernel.org, linux-kernel@...r.kernel.org, 
	linux-doc@...r.kernel.org
Subject: Re: [PATCH linux dev-6.6] A backport request for SY24655 driver in
 INA2XX driver for Linux kernel 6.6.

Hi Rush,

On Thu, 2025-02-06 at 11:07 +0800, Rush Chen wrote:
> From: Rush Chen <Rush_Chen@...ynn.com>
> 
> Summary:
> The driver SY24655 has been supported by INA2XX driver,
> since Linux kernel version 6.13.
> 
> Issue a backport request to Linux kernel 6.6.
> 
> Signed-off-by: Rush Chen <Rush_Chen@...ynn.com>

>From the way you've structured the subject prefix I expect you are
asking for this to be applied to OpenBMC's kernel fork (openbmc/linux).

If that's the case, this patch has no business bothering upstream
maintainers (Guenter, Jean, Jonathan) or the upstream mailing lists
(linux-hwmon@, linux-kernel@, linux-doc@). The only people this should
be sent to are myself and Joel, and the only list it should be sent to
is openbmc@.

If you send a backport patch for openbmc/linux and are using `git send-
email` to do so, then in nearly all cases you should use the `--
suppress-cc=all` option to make sure upstream maintainers and lists are
_not_ automatically copied on the mail.

However, if you wish this change to be back-ported to an _upstream_
stable tree (e.g. the v6.6 series), please _first_ familiarise yourself
with the stable tree rules, satisfy yourself that the change meets all
the requirements and constraints, and only then follow one of the
documented processes:

https://docs.kernel.org/process/stable-kernel-rules.html#stable-kernel-rules

If you have any questions do follow up with myself, Joel and the
OpenBMC mailing list, but make sure to exclude the upstream maintainers
and lists for now.

Thanks,

Andrew