From: "Thomas Weißschuh" <thomas@t-8ch.de>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: Jean Delvare <jdelvare@suse.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
Guenter Roeck <linux@roeck-us.net>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Heiner Kallweit <hkallweit1@gmail.com>
Subject: Re: [PATCH v2 1/4] i2c: smbus: only limit max banks to eight
Date: Tue, 9 Jul 2024 19:27:03 +0200 [thread overview]
Message-ID: <ee0b2612-afb4-4ccb-9afd-b0cfd7e26a6f@t-8ch.de> (raw)
In-Reply-To: <ibxkewtaxywpabogm776h7ty3grjquravsuwhtjbe2k4j7vlw6@enzxsfkk326z>
Hi Andi,
On 2024-07-05 13:56:24+0000, Andi Shyti wrote:
> On Fri, Jul 05, 2024 at 07:55:21AM GMT, Thomas Weißschuh wrote:
> > Jul 4, 2024 23:57:36 Andi Shyti <andi.shyti@kernel.org>:
> > > On Thu, Jun 27, 2024 at 07:48:11PM GMT, Thomas Weißschuh wrote:
> > >> If there are less than eight slots in total,
> > >> only probe those.
> > >> Now the code matches the comment "..., then limit slots to 8".
> > >>
> > >> Fixes: 8821c8376993 ("i2c: smbus: Prepare i2c_register_spd for usage on muxed segments")
> > >> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> > >
> > > I don't see the need for the Fixes here... was there a bug that
> > > has been fixed?
> >
> > More addresses are probed than are possible.
> > Which is a change from the old behavior and also
> > contradicts the comment.
> > IMO it's a bug. Probably not a big one and I'm not sure if user-observable.
> > Surely nothing for stable.
>
> The Fixes tag means that you want the patch to be backported to
> stable kernels. Someone will take the effort of taking all the
> new "Fixes:" and port them to older kernels.
It's my understanding that a Fixes tag itself is not enough for the
stable process. For that it also needs a "Cc: stable@vger.kernel.org" in
the patch or explicit notification of the stable team.
(Or being picked up by Autosel)
Anyways, I'll squash the commits and drop the Fixes tat, as there was no
bug as pointed out by Heiner.
> We want this when patches fix crashes, deadlocks, memory leaks,
> security holes, misbehaviours, earthquakes and floodings.
>
> Andi
>
> > But I'm not hung up on it and will drop that tag in the next revision.
next prev parent reply other threads:[~2024-07-09 17:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 17:48 [PATCH v2 0/4] i2c: smbus cleanups and SPD support for piix4 Thomas Weißschuh
2024-06-27 17:48 ` [PATCH v2 1/4] i2c: smbus: only limit max banks to eight Thomas Weißschuh
2024-07-04 21:57 ` Andi Shyti
2024-07-05 5:55 ` Thomas Weißschuh
2024-07-05 7:26 ` Heiner Kallweit
2024-07-05 11:56 ` Andi Shyti
2024-07-09 17:27 ` Thomas Weißschuh [this message]
2024-06-27 17:48 ` [PATCH v2 2/4] i2c: smbus: probe SPDs on a best-effort basis Thomas Weißschuh
2024-06-27 17:48 ` [PATCH v2 3/4] i2c: smbus: drop warning about muxed segments requirement Thomas Weißschuh
2024-06-27 17:48 ` [PATCH v2 4/4] i2c: piix4: Register SPDs Thomas Weißschuh
2024-06-28 23:09 ` Guenter Roeck
2024-06-29 7:19 ` Thomas Weißschuh
2024-06-29 14:01 ` Guenter Roeck
2024-06-29 14:09 ` Guenter Roeck
2024-07-04 21:45 ` Andi Shyti
2024-07-04 21:56 ` [PATCH v2 0/4] i2c: smbus cleanups and SPD support for piix4 Andi Shyti
2024-07-05 5:51 ` Thomas Weißschuh
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=ee0b2612-afb4-4ccb-9afd-b0cfd7e26a6f@t-8ch.de \
--to=thomas@t-8ch.de \
--cc=andi.shyti@kernel.org \
--cc=hkallweit1@gmail.com \
--cc=jdelvare@suse.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=wsa+renesas@sang-engineering.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