From: Hans de Goede <hdegoede@redhat.com>
To: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>,
irenic.rajneesh@gmail.com
Cc: david.e.box@intel.com, ilpo.jarvinen@linux.intel.com,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH] platform/x86/intel/pmc: make lnl_d3_fixup static
Date: Tue, 2 Jan 2024 13:31:12 +0100 [thread overview]
Message-ID: <f572489d-cdd7-4582-a355-ba0a917cf1f8@redhat.com> (raw)
In-Reply-To: <20231229020808.55840-1-jiapeng.chong@linux.alibaba.com>
Hi Jiapeng,
On 12/29/23 03:08, Jiapeng Chong wrote:
> The lnl_d3_fixup are not used outside the file lnl.c, so the
> modification is defined as static.
>
> drivers/platform/x86/intel/pmc/lnl.c:503:6: warning: no previous prototype for ‘lnl_d3_fixup’.
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=7811
> Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Thank you for your patch, but this has already been fixed
in the current version of the code, see:
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/tree/?h=for-next
Regards,
Hans
> ---
> drivers/platform/x86/intel/pmc/lnl.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/platform/x86/intel/pmc/lnl.c b/drivers/platform/x86/intel/pmc/lnl.c
> index 88b35931f5df..f18fdc68fd94 100644
> --- a/drivers/platform/x86/intel/pmc/lnl.c
> +++ b/drivers/platform/x86/intel/pmc/lnl.c
> @@ -500,7 +500,7 @@ const struct pmc_reg_map lnl_socm_reg_map = {
> * Set power state of select devices that do not have drivers to D3
> * so that they do not block Package C entry.
> */
> -void lnl_d3_fixup(void)
> +static void lnl_d3_fixup(void)
> {
> pmc_core_set_device_d3(LNL_IPU_PCI_DEV);
> pmc_core_set_device_d3(LNL_NPU_PCI_DEV);
prev parent reply other threads:[~2024-01-02 12:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-29 2:08 Jiapeng Chong
2024-01-02 12:31 ` Hans de Goede [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=f572489d-cdd7-4582-a355-ba0a917cf1f8@redhat.com \
--to=hdegoede@redhat.com \
--cc=abaci@linux.alibaba.com \
--cc=david.e.box@intel.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=irenic.rajneesh@gmail.com \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@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 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®