From: Greg KH <greg@kroah.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Sasha Levin <sashal@kernel.org>,
patches@lists.linux.dev, Jamie Iles <quic_jiles@quicinc.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH 5.10 005/147] i3c: remove i2c board info from i2c_dev_desc
Date: Thu, 23 Apr 2026 14:17:40 +0200 [thread overview]
Message-ID: <2026042332-anatomist-ditto-2252@gregkh> (raw)
In-Reply-To: <f7285cc36ec39c4a6cef633add170518f2e34b3a.camel@decadent.org.uk>
On Tue, Mar 17, 2026 at 02:13:42PM +0100, Ben Hutchings wrote:
> On Sat, 2026-02-28 at 13:15 -0500, Sasha Levin wrote:
> > From: Jamie Iles <quic_jiles@quicinc.com>
> >
> > [ Upstream commit 31b9887c7258ca47d9c665a80f19f006c86756b1 ]
> >
> > I2C board info is only required during adapter setup so there is no
> > requirement to keeping a pointer to it once running. To support dynamic
> > device addition we can't rely on board info - user-space creation
> > through sysfs won't have a boardinfo.
> [...]
>
> This was broken and needs commit 6cbf8b38dfe3 "i3c: fix uninitialized
> variable use in i2c setup" as a follow-up.
Sorrya bout that, now queued up.
greg k-h
next prev parent reply other threads:[~2026-04-23 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260228181736.1605592-1-sashal@kernel.org>
2026-02-28 18:16 ` [PATCH 5.10 054/147] regulator: core: Use ktime_get_boottime() to determine how long a regulator was off Sasha Levin
[not found] ` <20260228181736.1605592-5-sashal@kernel.org>
2026-03-17 13:13 ` [PATCH 5.10 005/147] i3c: remove i2c board info from i2c_dev_desc Ben Hutchings
2026-04-23 12:17 ` Greg KH [this message]
[not found] ` <20260228181736.1605592-22-sashal@kernel.org>
2026-03-17 14:16 ` [PATCH 5.10 022/147] s390/cio: Fix device lifecycle handling in css_alloc_subchannel() Ben Hutchings
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=2026042332-anatomist-ditto-2252@gregkh \
--to=greg@kroah.com \
--cc=alexandre.belloni@bootlin.com \
--cc=ben@decadent.org.uk \
--cc=patches@lists.linux.dev \
--cc=quic_jiles@quicinc.com \
--cc=sashal@kernel.org \
--cc=stable@vger.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