From: Nathan Chancellor <nathan@kernel.org>
To: irenic.rajneesh@gmail.com, david.e.box@intel.com,
hdegoede@redhat.com, ilpo.jarvinen@linux.intel.com,
rajvi.jingar@linux.intel.com
Cc: platform-driver-x86@vger.kernel.org, patches@lists.linux.dev,
Stephen Rothwell <sfr@canb.auug.org.au>,
Nathan Chancellor <nathan@kernel.org>
Subject: [PATCH 0/2] platform/x86/intel/pmc: Fix recent instances of -Wmissing-prototypes
Date: Fri, 22 Dec 2023 11:27:00 -0700 [thread overview]
Message-ID: <20231222-intel-pmc-missing-prototypes-v1-0-3f0d47377d4c@kernel.org> (raw)
As reported by Stephen at [1], there are a few instances of
-Wmissing-prototypes, which break the build with CONFIG_WERROR=y. This
series marks these functions as static because they are not used outside
of these translation units.
Feel free to squash these into the original changes if the branch is not
set in stone.
[1]: https://lore.kernel.org/all/20231222135412.6bd796cc@canb.auug.org.au/
---
Nathan Chancellor (2):
platform/x86/intel/pmc: Mark arl_d3_fixup() and arl_resume() as static
platform/x86/intel/pmc: Mark lnl_d3_fixup() and lnl_resume() as static
drivers/platform/x86/intel/pmc/arl.c | 4 ++--
drivers/platform/x86/intel/pmc/lnl.c | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
---
base-commit: 119652b855e6c96676406ee9a7f535f4db4e8eff
change-id: 20231222-intel-pmc-missing-prototypes-8fb5014b16b8
Best regards,
--
Nathan Chancellor <nathan@kernel.org>
next reply other threads:[~2023-12-22 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 18:27 Nathan Chancellor [this message]
2023-12-22 18:27 ` [PATCH 1/2] platform/x86/intel/pmc: Mark arl_d3_fixup() and arl_resume() as static Nathan Chancellor
2023-12-22 18:27 ` [PATCH 2/2] platform/x86/intel/pmc: Mark lnl_d3_fixup() and lnl_resume() " Nathan Chancellor
2023-12-28 9:07 ` [PATCH 0/2] platform/x86/intel/pmc: Fix recent instances of -Wmissing-prototypes Hans de Goede
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=20231222-intel-pmc-missing-prototypes-v1-0-3f0d47377d4c@kernel.org \
--to=nathan@kernel.org \
--cc=david.e.box@intel.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=irenic.rajneesh@gmail.com \
--cc=patches@lists.linux.dev \
--cc=platform-driver-x86@vger.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