From: Sasha Levin <sashal@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
patches@lists.linux.dev, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@nabladev.com, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
sr@sladewatkins.com
Subject: Re: [PATCH 5.15 000/410] 5.15.202-rc2 review
Date: Mon, 16 Mar 2026 21:30:44 -0400 [thread overview]
Message-ID: <abiuxFzZNLKbhz6F@laps> (raw)
In-Reply-To: <20260316220533.GD1329928@ax162>
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.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-03-17 1:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 16:09 [PATCH 5.15 000/410] 5.15.202-rc2 review Sasha Levin
2026-03-02 18:46 ` Florian Fainelli
2026-03-02 19:35 ` Brett A C Sheffield
2026-03-03 12:38 ` Ron Economos
2026-03-03 14:12 ` Jon Hunter
2026-03-03 16:59 ` Vijayendra Suman
2026-03-03 19:42 ` Mark Brown
2026-03-04 6:12 ` Hardik Garg
2026-03-05 22:08 ` Nathan Chancellor
2026-03-16 22:05 ` Nathan Chancellor
2026-03-17 1:30 ` Sasha Levin [this message]
2026-03-17 4:42 ` Greg Kroah-Hartman
2026-03-17 7:39 ` Greg Kroah-Hartman
2026-03-18 2:35 ` Nathan Chancellor
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=abiuxFzZNLKbhz6F@laps \
--to=sashal@kernel.org \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=nathan@kernel.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@nabladev.com \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=sr@sladewatkins.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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