linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Mark Gross <markgross@kernel.org>
Cc: Rajvi Jingar <rajvi.jingar@linux.intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the drivers-x86 tree
Date: Fri, 22 Dec 2023 15:10:45 +0100	[thread overview]
Message-ID: <3d087d6b-2ab5-4113-99aa-4dd6b9d88b22@redhat.com> (raw)
In-Reply-To: <20231222135412.6bd796cc@canb.auug.org.au>

Hi All,

On 12/22/23 03:54, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the drivers-x86 tree, today's linux-next build (x86_64
> allmodconfig) produced these warnings:
> 
> drivers/platform/x86/intel/pmc/arl.c:680:6: warning: no previous prototype for 'arl_d3_fixup' [-Wmissing-prototypes]
>   680 | void arl_d3_fixup(void)
>       |      ^~~~~~~~~~~~
> drivers/platform/x86/intel/pmc/arl.c:685:5: warning: no previous prototype for 'arl_resume' [-Wmissing-prototypes]
>   685 | int arl_resume(struct pmc_dev *pmcdev)
>       |     ^~~~~~~~~~
> drivers/platform/x86/intel/pmc/lnl.c:503:6: warning: no previous prototype for 'lnl_d3_fixup' [-Wmissing-prototypes]
>   503 | void lnl_d3_fixup(void)
>       |      ^~~~~~~~~~~~
> drivers/platform/x86/intel/pmc/lnl.c:509:5: warning: no previous prototype for 'lnl_resume' [-Wmissing-prototypes]
>   509 | int lnl_resume(struct pmc_dev *pmcdev)
>       |     ^~~~~~~~~~
> 
> Introduced by commits
> 
>   f34dcf397286 ("platform/x86/intel/pmc: Add Arrow Lake S support to intel_pmc_core driver")
>   119652b855e6 ("platform/x86/intel/pmc: Add Lunar Lake M support to intel_pmc_core driver")

Ravji, can you please submit some fixes for these ?

Please split out the fixes into one per file, then I'll squash
them into the original commits.

Stephen, thank you for reporting these.

Regards,

Hans




  reply	other threads:[~2023-12-22 14:10 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-22  2:54 linux-next: build warnings after merge of the drivers-x86 tree Stephen Rothwell
2023-12-22 14:10 ` Hans de Goede [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-09  1:28 Stephen Rothwell
2023-03-09  8:48 ` Hans de Goede
2023-03-09 10:40   ` Orlando Chamberlain
2022-03-01  9:16 Stephen Rothwell
2022-03-01 13:53 ` Hans de Goede
2022-03-24  7:33 ` Stephen Rothwell
2022-03-24  7:39   ` Hans de Goede
2022-03-24 11:22     ` Stephen Rothwell
2022-03-24 13:01       ` Hans de Goede
2022-03-24 13:04       ` Hans de Goede
2022-03-24 21:55         ` Stephen Rothwell
2022-03-25  5:27           ` Mauro Carvalho Chehab
2022-03-25  6:18             ` Mauro Carvalho Chehab
2021-10-21  7:47 Stephen Rothwell
2021-10-21  9:07 ` Vadim Pasternak
2021-10-21 20:04   ` Stephen Rothwell
2021-10-21 21:10     ` Jonathan Corbet
2021-10-22  9:02       ` Hans de Goede
2021-10-21  9:14 ` Hans de Goede
2021-10-21 20:02   ` Stephen Rothwell
2020-11-05  6:55 Stephen Rothwell
2011-02-22  5:13 Stephen Rothwell
2011-02-22 10:36 ` Colin Ian King
2010-12-08  2:32 Stephen Rothwell

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=3d087d6b-2ab5-4113-99aa-4dd6b9d88b22@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=markgross@kernel.org \
    --cc=rajvi.jingar@linux.intel.com \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).