linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Sudeep Holla <sudeep.holla@arm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	"Rafael J . Wysocki" <rafael@kernel.org>
Cc: kbuild-all@lists.01.org, Sudeep Holla <sudeep.holla@arm.com>
Subject: [RFC PATCH] ACPI: PCC: pcc_ctx can be static
Date: Thu, 6 Jan 2022 01:45:56 +0800	[thread overview]
Message-ID: <20220105174554.GA29945@1e936cf764ba> (raw)
In-Reply-To: <20220103155838.616580-1-sudeep.holla@arm.com>

drivers/acpi/acpi_pcc.c:34:22: warning: symbol 'pcc_ctx' was not declared. Should it be static?

Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
 acpi_pcc.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/acpi/acpi_pcc.c b/drivers/acpi/acpi_pcc.c
index 64552fdb73470..9df4d740b52a6 100644
--- a/drivers/acpi/acpi_pcc.c
+++ b/drivers/acpi/acpi_pcc.c
@@ -31,7 +31,7 @@ struct pcc_data {
 	struct acpi_pcc_info ctx;
 };
 
-struct acpi_pcc_info pcc_ctx;
+static struct acpi_pcc_info pcc_ctx;
 
 static void pcc_rx_callback(struct mbox_client *cl, void *m)
 {

  parent reply	other threads:[~2022-01-05 17:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03 15:58 [PATCH v2] ACPI: PCC: Implement OperationRegion handler for the PCC Type 3 subtype Sudeep Holla
2022-01-04  8:01 ` kernel test robot
2022-01-05 17:45 ` kernel test robot [this message]
2022-01-06 14:12   ` [RFC PATCH] ACPI: PCC: pcc_ctx can be static Sudeep Holla
2022-01-12 18:42     ` Rafael J. Wysocki
2022-01-05 17:50 ` [PATCH v2] ACPI: PCC: Implement OperationRegion handler for the PCC Type 3 subtype kernel test robot
2022-01-05 21:46 ` kernel test robot

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=20220105174554.GA29945@1e936cf764ba \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=sudeep.holla@arm.com \
    --subject='Re: [RFC PATCH] ACPI: PCC: pcc_ctx can be static' \
    /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

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).