From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: 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, 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,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH 5.10 000/161] 5.10.249-rc1 review
Date: Thu, 5 Feb 2026 15:01:23 +0100 [thread overview]
Message-ID: <2026020553-dazzling-quack-dd44@gregkh> (raw)
In-Reply-To: <f6280336-4e59-47ed-876a-bfb62252ae52@nvidia.com>
On Wed, Feb 04, 2026 at 07:54:47PM +0000, Jon Hunter wrote:
> Hi Greg,
>
> On 04/02/2026 14:37, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.10.249 release.
> > There are 161 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Fri, 06 Feb 2026 14:38:23 +0000.
> > Anything received after that time might be too late.
> >
> > The whole patch series can be found in one patch at:
> > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.249-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-5.10.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
> >
> > -------------
> > Pseudo-Shortlog of commits:
>
> ...
>
> >
> > Johan Hovold <johan@kernel.org>
> > dmaengine: at_hdmac: fix device leak on of_dma_xlate()
>
> The above commit is causing the following build error for 32-bit ARM with
> multi_v7_defconfig ...
>
> drivers/dma/at_hdmac.c: In function ‘atc_config’:
> drivers/dma/at_hdmac.c:1323:34: warning: unused variable ‘atslave’
> [-Wunused-variable]
> 1323 | struct at_dma_slave *atslave;
> | ^~~~~~~
> drivers/dma/at_hdmac.c: In function ‘atc_free_chan_resources’:
> drivers/dma/at_hdmac.c:1583:9: error: ‘atslave’ undeclared (first use in
> this function)
> 1583 | atslave = chan->private;
> | ^~~~~~~
>
>
> This is also seen with linux-5.15.y and linux-6.1.y branches. Linux-6.6.y
> and newer are building fine.
Ah, looks like the patch fuzz caused the variable to be declared in the
wrong function, let me go fix that up...
thanks,
greg k-h
prev parent reply other threads:[~2026-02-05 14:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260204143851.755002596@linuxfoundation.org>
2026-02-04 19:54 ` [PATCH 5.10 000/161] 5.10.249-rc1 review Jon Hunter
2026-02-05 14:01 ` Greg Kroah-Hartman [this message]
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=2026020553-dazzling-quack-dd44@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hargar@microsoft.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--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