public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: stable@vger.kernel.org, Jean Delvare <jdelvare@suse.com>,
	Wolfram Sang <wsa@kernel.org>,
	linux-i2c@vger.kernel.org
Subject: Re: Please backport commit 13e3a512a290 (i2c: smbus: Support up to 8 SPD EEPROMs)
Date: Thu, 28 Mar 2024 07:10:50 +0100	[thread overview]
Message-ID: <2024032814-colony-observant-4e42@gregkh> (raw)
In-Reply-To: <4fa53db0-358d-4e30-bcfa-745cab71fa72@molgen.mpg.de>

On Wed, Mar 27, 2024 at 09:35:38PM +0100, Paul Menzel wrote:
> 
> [Cc: +I2C folks]
> 
> 
> Dear Greg,
> 
> 
> Am 27.03.24 um 17:52 schrieb Greg KH:
> > On Wed, Mar 27, 2024 at 04:13:26PM +0100, Paul Menzel wrote:
> 
> > > Please apply commit 13e3a512a290 (i2c: smbus: Support up to 8 SPD EEPROMs)
> > > [1] to the stable series to get rid of a warning and to support more SPDs.
> > > That commit is present since v6.8-rc1.
> > 
> > How far back?
> 
> I’d say 6.1.
> 
> > But isn't this a new feature, why is it needed in older kernels?
> > It's not a fix for a regression.
> decode-dimm does not work on systems with more than four SPD EEPROMs, so I’d
> say it’s a fix.

But it's never worked on such systems so it's not a regression fix,
right?

Anyway, I'll defer to the i2c maintainers as to what they want to have
happen here, as they did not originally tag this commit for stable
inclusion.

thanks,

greg k-h

  reply	other threads:[~2024-03-28  6:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-27 15:13 Please backport commit 13e3a512a290 (i2c: smbus: Support up to 8 SPD EEPROMs) Paul Menzel
2024-03-27 16:52 ` Greg KH
2024-03-27 20:35   ` Paul Menzel
2024-03-28  6:10     ` Greg KH [this message]
2024-03-28 14:51       ` Jean DELVARE

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=2024032814-colony-observant-4e42@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=jdelvare@suse.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=pmenzel@molgen.mpg.de \
    --cc=stable@vger.kernel.org \
    --cc=wsa@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