From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, 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, allen.lkml@gmail.com, broonie@kernel.org
Subject: Re: [PATCH 6.10 000/263] 6.10.5-rc1 review
Date: Fri, 16 Aug 2024 10:38:08 +0200 [thread overview]
Message-ID: <2024081616-gents-snowcap-0e5f@gregkh> (raw)
In-Reply-To: <8852e518-3867-4802-adea-0c0ee68d1010@roeck-us.net>
On Thu, Aug 15, 2024 at 07:21:00AM -0700, Guenter Roeck wrote:
> On 8/12/24 09:00, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.10.5 release.
> > There are 263 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, 14 Aug 2024 16:00:26 +0000.
> > Anything received after that time might be too late.
> >
>
> I see various allmodconfig build failures on v6.10.5.
>
> Example from arm:
>
> Building arm:allmodconfig ... failed
> --------------
> Error log:
> drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_mst_types.c:1581:13: error: 'is_dsc_common_config_possible' defined but not used [-Werror=unused-function]
> 1581 | static bool is_dsc_common_config_possible(struct dc_stream_state *stream,
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_mst_types.c:1569:21: error: 'kbps_from_pbn' defined but not used [-Werror=unused-function]
> 1569 | static unsigned int kbps_from_pbn(unsigned int pbn)
>
> The functions are built and used conditionally in mainline, behind CONFIG_DRM_AMD_DC_FP.
> The conditional is missing in v6.10.5 (and v6.10.6-rc1).
Odd that other allmodconfig builds passed :(
I'll dig up where that conditional showed up, thanks for letting us
know....
Ah, looks like it showed up in 00c391102abc ("drm/amd/display: Add misc
DC changes for DCN401"), gotta love "fix a bunch of things" type of
commits...
{sigh}
greg k-h
next prev parent reply other threads:[~2024-08-16 8:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 16:00 Greg Kroah-Hartman
2024-08-12 20:54 ` Pavel Machek
2024-08-13 7:09 ` Naresh Kamboju
2024-08-13 11:32 ` Peter Schneider
2024-08-13 12:23 ` Mark Brown
2024-08-13 16:16 ` Markus Reichelt
2024-08-13 17:33 ` Florian Fainelli
2024-08-13 18:41 ` Jon Hunter
2024-08-13 19:34 ` Ron Economos
2024-08-15 14:21 ` Guenter Roeck
2024-08-16 8:38 ` Greg Kroah-Hartman [this message]
2024-08-16 8:42 ` Greg Kroah-Hartman
2024-08-16 14:43 ` Guenter Roeck
2024-08-16 22:13 ` Nathan Chancellor
2024-08-12 16:48 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=2024081616-gents-snowcap-0e5f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=broonie@kernel.org \
--cc=conor@kernel.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
all inboxes | Powered by JetHome®