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

[Rush Chen/WYHQ/Wiwynn]

Hi Andrew,

Thanks for your reply.
I will resend an email to the relevant.
If there is still any problem, please let me know.
Thank you.

Rush

-----Original Message-----
From: Andrew Jeffery <andrew@xxxxxxxxxxxxxxxxxxxx>
Sent: Friday, February 7, 2025 7:48 AM
To: Rush Chen/WYHQ/Wiwynn <Rush_Chen@xxxxxxxxxx>; openbmc@xxxxxxxxxxxxxxxx; andrew@xxxxxxxx; Guenter Roeck <linux@xxxxxxxxxxxx>; Jean Delvare <jdelvare@xxxxxxxx>; Jonathan Corbet <corbet@xxxxxxx>
Cc: linux-hwmon@xxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; linux-doc@xxxxxxxxxxxxxxx
Subject: Re: [PATCH linux dev-6.6] A backport request for SY24655 driver in INA2XX driver for Linux kernel 6.6.

[You don't often get email from andrew@xxxxxxxxxxxxxxxxxxxx. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]

 [External Sender]

Hi Rush,

On Thu, 2025-02-06 at 11:07 +0800, Rush Chen wrote:
> From: Rush Chen <Rush_Chen@xxxxxxxxxx>
>
> 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@xxxxxxxxxx>

>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
WIWYNN PROPRIETARY
This email (and any attachments) contains proprietary or confidential information and is for the sole use of its intended recipient. Any unauthorized review, use, copying or distribution of this email or the content of this email is strictly prohibited. If you are not the intended recipient, please notify the sender and delete this email immediately.