From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jaak Ristioja <jaak@ristioja.ee>
Cc: stable@vger.kernel.org
Subject: Re: drivers/platform/x86/amd/pmc.c compile error in 6.0.6
Date: Sun, 30 Oct 2022 15:20:54 +0100 [thread overview]
Message-ID: <Y16IRs2ogZBxGMS3@kroah.com> (raw)
In-Reply-To: <ddeed421-cf75-4a44-4f5d-f26cd0359b78@ristioja.ee>
On Sun, Oct 30, 2022 at 03:44:55PM +0200, Jaak Ristioja wrote:
> On 30.10.22 09:23, Greg Kroah-Hartman wrote:
> > On Sun, Oct 30, 2022 at 01:51:59AM +0300, Jaak Ristioja wrote:
> > > Hello,
> > >
> > > The following error popped up when compiling Linux kernel version 6.0.6:
> > >
> > > drivers/platform/x86/amd/pmc.c: In function 'amd_pmc_verify_czn_rtc':
> > > drivers/platform/x86/amd/pmc.c:640:22: error: implicit declaration of
> > > function 'amd_pmc_get_smu_version' [-Werror=implicit-function-declaration]
> > > 640 | rc = amd_pmc_get_smu_version(pdev);
> > > | ^~~~~~~~~~~~~~~~~~~~~~~
> > >
> > > This function call was introduced backported with commit e9847175b266 with
> > > the subject line "platform/x86/amd: pmc: Read SMU version during suspend on
> > > Cezanne systems".
> > >
> > > Please note that amd_pmc_get_smu_version() is defined in an #ifdef
> > > CONFIG_DEBUG_FS block, but the new function call is compiled regardless of
> > > CONFIG_DEBUG_FS, causing the aforementioned error when building without the
> > > Debug Filesystem.
> >
> > Ah, good catch. Is this issue also there in Linus's tree? If not, any
> > hint on what commit fixed it?
>
> It looks like applying commit b37fe34c8309 titled "platform/x86/amd: pmc:
> remove CONFIG_DEBUG_FS checks" fixes the compile error. Hope it helps :)
Thanks a lot, that does help. Patch is now queued up.
greg k-h
prev parent reply other threads:[~2022-10-30 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-29 22:51 drivers/platform/x86/amd/pmc.c compile error in 6.0.6 Jaak Ristioja
2022-10-30 7:23 ` Greg Kroah-Hartman
2022-10-30 13:44 ` Jaak Ristioja
2022-10-30 14:20 ` 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=Y16IRs2ogZBxGMS3@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jaak@ristioja.ee \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.