From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Salvatore Bonaccorso <carnil@debian.org>
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, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de
Subject: Re: [PATCH 5.10 000/381] 5.10.180-rc1 review
Date: Wed, 17 May 2023 10:28:19 +0200 [thread overview]
Message-ID: <2023051756-shield-reenter-80fe@gregkh> (raw)
In-Reply-To: <ZGNATKe3U0oXHICX@eldamar.lan>
On Tue, May 16, 2023 at 10:35:24AM +0200, Salvatore Bonaccorso wrote:
> Hi Greg,
>
> On Mon, May 15, 2023 at 06:24:11PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.10.180 release.
> > There are 381 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 Wed, 17 May 2023 16:16:37 +0000.
> > Anything received after that time might be too late.
>
> The build fails here with:
>
> sound/soc/intel/boards/sof_sdw.c:187:6: error: ‘RT711_JD2_100K’ undeclared here (not in a function)
> 187 | RT711_JD2_100K),
> | ^~~~~~~~~~~~~~
> make[7]: *** [scripts/Makefile.build:286: sound/soc/intel/boards/sof_sdw.o] Error 1
> make[6]: *** [scripts/Makefile.build:503: sound/soc/intel/boards] Error 2
> make[5]: *** [scripts/Makefile.build:503: sound/soc/intel] Error 2
> make[4]: *** [scripts/Makefile.build:503: sound/soc] Error 2
> make[3]: *** [Makefile:1828: sound] Error 2
>
> I did mention it in
> https://lore.kernel.org/stable/ZFuHEML1r5Xd6S7g@eldamar.lan/ as well but I
> guess it felt trough the cracks back then.
Sorry I missed this back then, now dropped. Interesting that almost no
other build testing caught this, it's a hard driver to enable...
thanks,
greg k-h
next prev parent reply other threads:[~2023-05-17 8:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 16:24 [PATCH 5.10 000/381] 5.10.180-rc1 review Greg Kroah-Hartman
2023-05-15 16:29 ` [PATCH 5.10 317/381] rxrpc: Fix hard call timeout units Greg Kroah-Hartman
2023-05-15 20:10 ` [PATCH 5.10 000/381] 5.10.180-rc1 review Chris Paterson
2023-05-16 1:30 ` Shuah Khan
2023-05-16 8:35 ` Salvatore Bonaccorso
2023-05-17 8:28 ` Greg Kroah-Hartman [this message]
2023-05-16 9:14 ` Sudip Mukherjee (Codethink)
2023-05-17 8:51 ` Greg Kroah-Hartman
2023-05-17 9:41 ` Naresh Kamboju
2023-05-17 9:51 ` Greg Kroah-Hartman
2023-05-17 19:52 ` Sudip Mukherjee (Codethink)
2023-05-22 18:58 ` Greg Kroah-Hartman
2023-05-16 18:03 ` Naresh Kamboju
2023-05-17 2:49 ` Guenter Roeck
2023-05-17 7:55 ` Jon Hunter
2023-05-20 21:39 ` Greg Thelen
2023-05-26 18:18 ` Greg Kroah-Hartman
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=2023051756-shield-reenter-80fe@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=carnil@debian.org \
--cc=f.fainelli@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@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=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