mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Rush Chen <rush_chen@wiwynn.com>,
	openbmc@lists.ozlabs.org, andrew@aj.id.au,
	 Guenter Roeck <linux@roeck-us.net>,
	Jean Delvare <jdelvare@suse.com>,
	Jonathan Corbet <corbet@lwn.net>
Cc: linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
	 linux-doc@vger.kernel.org
Subject: Re: [PATCH linux dev-6.6] A backport request for SY24655 driver in INA2XX driver for Linux kernel 6.6.
Date: Fri, 07 Feb 2025 10:18:29 +1030	[thread overview]
Message-ID: <9f0447151e6574d74e7fa9cbbb50d8e970059273.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20250206030747.268165-1-rush_chen@wiwynn.com>

Hi Rush,

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

  reply	other threads:[~2025-02-06 23:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-06  3:07 Rush Chen
2025-02-06 23:48 ` Andrew Jeffery [this message]
2025-02-07  6:02   ` Rush Chen/WYHQ/Wiwynn

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=9f0447151e6574d74e7fa9cbbb50d8e970059273.camel@codeconstruct.com.au \
    --to=andrew@codeconstruct.com.au \
    --cc=andrew@aj.id.au \
    --cc=corbet@lwn.net \
    --cc=jdelvare@suse.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=openbmc@lists.ozlabs.org \
    --cc=rush_chen@wiwynn.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

all inboxes | Powered by JetHome®