From: Ron Economos <re@w6rz.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Cc: 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, allen.lkml@gmail.com, broonie@kernel.org
Subject: Re: [PATCH 6.1 00/86] 6.1.104-rc2 review
Date: Thu, 8 Aug 2024 04:55:27 -0700 [thread overview]
Message-ID: <96b86f9b-c516-9742-5e33-e5cbfbed10b3@w6rz.net> (raw)
In-Reply-To: <20240808091131.014292134@linuxfoundation.org>
On 8/8/24 2:11 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.1.104 release.
> There are 86 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 Sat, 10 Aug 2024 09:11:02 +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/v6.x/stable-review/patch-6.1.104-rc2.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.1.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
>
I'm seeing a build failure.
sound/pci/hda/patch_conexant.c:273:10: error: ‘const struct
hda_codec_ops’ has no member named ‘suspend’
273 | .suspend = cx_auto_suspend,
| ^~~~~~~
sound/pci/hda/patch_conexant.c:273:20: error: initialization of ‘void
(*)(struct hda_codec *, hda_nid_t, unsigned int)’ {aka ‘void (*)(struct
hda_codec *, short unsigned int, unsigned int)’} from incompatible
pointer type ‘int (*)(struct hda_codec *)’
[-Werror=incompatible-pointer-types]
273 | .suspend = cx_auto_suspend,
| ^~~~~~~~~~~~~~~
sound/pci/hda/patch_conexant.c:273:20: note: (near initialization for
‘cx_auto_patch_ops.set_power_state’)
sound/pci/hda/patch_conexant.c:274:10: error: ‘const struct
hda_codec_ops’ has no member named ‘check_power_status’; did you mean
‘set_power_state’?
274 | .check_power_status = snd_hda_gen_check_power_status,
| ^~~~~~~~~~~~~~~~~~
| set_power_state
sound/pci/hda/patch_conexant.c:274:31: error:
‘snd_hda_gen_check_power_status’ undeclared here (not in a function);
did you mean ‘snd_hda_check_power_state’?
274 | .check_power_status = snd_hda_gen_check_power_status,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| snd_hda_check_power_state
This is triggered because my config does not include CONFIG_PM. But the
error is caused by upstream patch
9e993b3d722fb452e274e1f8694d8940db183323 "ALSA: hda: codec: Reduce
CONFIG_PM dependencies" being missing. This patch removes the #ifdef
CONFIG_PM in the hda_codec_ops structure. So if CONFIG_PM is not set,
some structure members are missing and the the build fails.
next prev parent reply other threads:[~2024-08-08 11:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 9:11 Greg Kroah-Hartman
2024-08-08 10:33 ` Salvatore Bonaccorso
2024-08-10 5:02 ` Salvatore Bonaccorso
2024-08-10 21:36 ` Quentin Monnet
2024-08-11 15:23 ` Greg Kroah-Hartman
2024-08-08 11:03 ` Miguel Ojeda
2024-08-08 11:55 ` Ron Economos [this message]
2024-08-08 14:43 ` Ron Economos
2024-08-08 16:45 ` Ron Economos
2024-08-11 10:14 ` Greg Kroah-Hartman
2024-08-08 16:58 ` Pavel Machek
2024-08-08 17:03 ` Anders Roxell
2024-08-09 5:46 ` Peter Schneider
2024-08-09 10:51 ` Jon Hunter
2024-08-09 11:58 ` Shreeya Patel
2024-08-09 18:35 ` Florian Fainelli
2024-08-12 21:49 ` Guenter Roeck
2024-08-13 2:44 ` Guenter Roeck
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=96b86f9b-c516-9742-5e33-e5cbfbed10b3@w6rz.net \
--to=re@w6rz.net \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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®