public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
	Sasha Levin <sashal@kernel.org>,
	stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
	patches@kernelci.org, lkft-triage@lists.linaro.org,
	pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
	conor@kernel.org, hargar@microsoft.com, broonie@kernel.org,
	Dan Carpenter <dan.carpenter@linaro.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Anders Roxell <anders.roxell@linaro.org>,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Alexander Stein <alexander.stein@ew.tq-group.com>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Michal Suchanek <msuchanek@suse.de>,
	Nicolai Stange <nstange@suse.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [PATCH 6.12 000/826] 6.12.2-rc1 review
Date: Thu, 5 Dec 2024 10:23:51 +0100	[thread overview]
Message-ID: <2024120504-verbose-hurried-eb52@gregkh> (raw)
In-Reply-To: <20241204164853.GA3356373@thelio-3990X>

On Wed, Dec 04, 2024 at 09:48:53AM -0700, Nathan Chancellor wrote:
> On Wed, Dec 04, 2024 at 06:30:47PM +0530, Naresh Kamboju wrote:
> > On Tue, 3 Dec 2024 at 21:06, Greg Kroah-Hartman
> > <gregkh@linuxfoundation.org> wrote:
> > > The whole patch series can be found in one patch at:
> > >         https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.12.2-rc1.gz
> > > or in the git tree and branch at:
> > >         git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.12.y
> > > and the diffstat can be found below
> ...
> > 1) The allmodconfig builds failed on arm64, arm, riscv and x86_64
> >      due to following build warnings / errors.
> > 
> > Build errors for allmodconfig:
> > --------------
> > drivers/gpu/drm/imx/ipuv3/parallel-display.c:75:3: error: variable
> > 'num_modes' is uninitialized when used here [-Werror,-Wuninitialized]
> >    75 |                 num_modes++;
> >       |                 ^~~~~~~~~
> > drivers/gpu/drm/imx/ipuv3/parallel-display.c:55:15: note: initialize
> > the variable 'num_modes' to silence this warning
> >    55 |         int num_modes;
> >       |                      ^
> >       |                       = 0
> > 1 error generated.
> > make[8]: *** [scripts/Makefile.build:229:
> > drivers/gpu/drm/imx/ipuv3/parallel-display.o] Error 1
> 
> Introduced by backporting commit 5f6e56d3319d ("drm/imx:
> parallel-display: switch to drm_panel_bridge") without
> commit f94b9707a1c9 ("drm/imx: parallel-display: switch to
> imx_legacy_bridge / drm_bridge_connector"). The latter change also had a
> follow up fix in commit ef214002e6b3 ("drm/imx: parallel-display: add
> legacy bridge Kconfig dependency").
> 
> > drivers/gpu/drm/imx/ipuv3/imx-ldb.c:143:3: error: variable 'num_modes'
> > is uninitialized when used here [-Werror,-Wuninitialized]
> >   143 |                 num_modes++;
> >       |                 ^~~~~~~~~
> > drivers/gpu/drm/imx/ipuv3/imx-ldb.c:133:15: note: initialize the
> > variable 'num_modes' to silence this warning
> >   133 |         int num_modes;
> >       |                      ^
> >       |                       = 0
> > 1 error generated.
> 
> Introduced by backporting commit 5c5843b20bbb ("drm/imx: ldb: switch to
> drm_panel_bridge") without commit 4c3d525f6573 ("drm/imx: ldb: switch to
> imx_legacy_bridge / drm_bridge_connector").
> 
> These are both upstream patch series bisectability issues, not anything
> that stable specifically did, as the num_nodes initialization was
> removed by the first change but the entire function containing num_nodes
> was removed by the second change so when the series was taken atomically
> upstream, nobody notices. However, I do wonder why these patches are
> being picked up, as they don't really read like fixes to me and the
> cover letter of the original series does not really make it seem like it
> either.

Thanks, I'll just rip them both out now.

greg k-h

  reply	other threads:[~2024-12-05  9:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03 14:35 [PATCH 6.12 000/826] 6.12.2-rc1 review Greg Kroah-Hartman
2024-12-03 14:43 ` [PATCH 6.12 512/826] m68k: coldfire/device.c: only build FEC when HW macros are defined Greg Kroah-Hartman
2024-12-03 14:48 ` [PATCH 6.12 788/826] net/9p/usbg: fix handling of the failed kzalloc() memory allocation Greg Kroah-Hartman
2024-12-03 21:32 ` [PATCH 6.12 000/826] 6.12.2-rc1 review Peter Schneider
2024-12-03 22:07 ` Mark Brown
2024-12-03 22:36 ` Florian Fainelli
2024-12-04  0:24 ` SeongJae Park
2024-12-04  7:09 ` Ron Economos
2024-12-04 13:00 ` Naresh Kamboju
2024-12-04 16:48   ` Nathan Chancellor
2024-12-05  9:23     ` Greg Kroah-Hartman [this message]
2024-12-04 16:53 ` Shuah Khan
2024-12-04 18:44 ` Miguel Ojeda
2024-12-05 11:13 ` Muhammad Usama Anjum
2024-12-05 11:22 ` Pavel Machek
2024-12-05 14:39 ` Jon Hunter
2024-12-05 14:46   ` Jon Hunter
2024-12-05 15:46 ` Peter Jung
2024-12-05 17:51   ` Linus Torvalds
2024-12-06  5:48     ` Greg Kroah-Hartman
  -- strict thread matches above, loose matches on Subject: below --
2024-12-03 22:23 Ronald Warsow

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=2024120504-verbose-hurried-eb52@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=anders.roxell@linaro.org \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=dan.carpenter@linaro.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=f.fainelli@gmail.com \
    --cc=hargar@microsoft.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=mpe@ellerman.id.au \
    --cc=msuchanek@suse.de \
    --cc=naresh.kamboju@linaro.org \
    --cc=nathan@kernel.org \
    --cc=nstange@suse.com \
    --cc=p.zabel@pengutronix.de \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@denx.de \
    --cc=rwarsow@gmx.de \
    --cc=sashal@kernel.org \
    --cc=shuah@kernel.org \
    --cc=srw@sladewatkins.net \
    --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