Re: [PATCH 5.15 000/410] 5.15.202-rc2 review

[Greg Kroah-Hartman <gregkh@linuxfoundation.org>]

On Tue, Mar 17, 2026 at 05:42:14AM +0100, Greg Kroah-Hartman wrote:
> On Mon, Mar 16, 2026 at 09:30:44PM -0400, Sasha Levin wrote:
> > On Mon, Mar 16, 2026 at 03:05:33PM -0700, Nathan Chancellor wrote:
> > > On Thu, Mar 05, 2026 at 03:08:09PM -0700, Nathan Chancellor wrote:
> > > > On Mon, Mar 02, 2026 at 11:09:55AM -0500, Sasha Levin wrote:
> > > > > Jamie Iles (1):
> > > > >   i3c: remove i2c board info from i2c_dev_desc
> > > > 
> > > > You missed commit 6cbf8b38dfe3 ("i3c: fix uninitialized variable use in
> > > > i2c setup") as a fix for this one, as rightfully pointed out by clang:
> > > > 
> > > >   https://lore.kernel.org/177198114226.2577.15577566399399369654@d14e337afe00/
> > > > 
> > > >   $ make -skj"$(nproc)" ARCH=x86_64 LLVM=1 mrproper allmodconfig drivers/i3c/master.o
> > > >   drivers/i3c/master.c:2203:3: error: variable 'i2cdev' is uninitialized when used here [-Werror,-Wuninitialized]
> > > >    2203 |                 i2cdev->dev = i2c_new_client_device(adap, &i2cboardinfo->base);
> > > >         |                 ^~~~~~
> > > > 
> > > > I guess that report was missed because it was not actually addressed to
> > > > anyone?
> > > > 
> > > > FWIW, this patch appeared in a previous 5.15-rc release but Ben
> > > > rightfully pointed out it really was not necessary and Greg said he
> > > > would fix it up by hand:
> > > > 
> > > >   https://lore.kernel.org/2026011724-florist-brook-5f1f@gregkh/
> > > > 
> > > > Guess that never happened?
> > > 
> > > Ping? I don't see 6cbf8b38dfe3 queued up in 5.15 and this continues to
> > > break our builds:
> > > 
> > >  https://github.com/ClangBuiltLinux/continuous-integration2/actions/runs/23093834605
> > 
> > Hm, I queued it up, but looks like Greg dropped it:
> > 
> > 	https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/commit/?id=7c0d6910ad
> > 
> > I'm not sure why.
> 
> I am guessing that it broke some type of build, and so I figured it was
> safer to just drop them all.  I'll try it again later today, sorry about
> that...

Wait, I removed them all, as that should have fixed the issue (I removed
the offending commit that was originally causing the build problem
here.)

Nathan, what errors are you seeing now?  None of these changes are in a
release, and I don't see any i3c patches in the current queue.

confused,

greg k-h