From: Hans de Goede <hdegoede@redhat.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Hans de Goede <hdegoede@redhat.com>,
linux-leds@vger.kernel.org,
Henning Schild <henning.schild@siemens.com>,
kernel test robot <lkp@intel.com>
Subject: [PATCH 1/2] leds: simatic-ipc-leds: Make simatic_ipc_led_mem_res static
Date: Mon, 17 Jan 2022 12:21:08 +0100 [thread overview]
Message-ID: <20220117112109.215695-1-hdegoede@redhat.com> (raw)
simatic_ipc_led_mem_res is not used outside of the driver, make it static.
Cc: Henning Schild <henning.schild@siemens.com>
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
---
drivers/leds/simple/simatic-ipc-leds.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/leds/simple/simatic-ipc-leds.c b/drivers/leds/simple/simatic-ipc-leds.c
index ff2c96e73241..179110448659 100644
--- a/drivers/leds/simple/simatic-ipc-leds.c
+++ b/drivers/leds/simple/simatic-ipc-leds.c
@@ -39,7 +39,7 @@ static struct simatic_ipc_led simatic_ipc_leds_io[] = {
};
/* the actual start will be discovered with PCI, 0 is a placeholder */
-struct resource simatic_ipc_led_mem_res = DEFINE_RES_MEM_NAMED(0, SZ_4K, KBUILD_MODNAME);
+static struct resource simatic_ipc_led_mem_res = DEFINE_RES_MEM_NAMED(0, SZ_4K, KBUILD_MODNAME);
static void *simatic_ipc_led_memory;
--
2.33.1
next reply other threads:[~2022-01-17 11:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 11:21 Hans de Goede [this message]
2022-01-17 11:21 ` [PATCH 2/2] leds: simatic-ipc-leds: Don't directly deref ioremap_resource() returned ptr Hans de Goede
2022-01-28 9:30 ` Henning Schild
2022-01-28 9:37 ` Hans de Goede
2022-01-28 15:26 ` Henning Schild
2022-02-03 10:43 ` Hans de Goede
2022-02-17 11:17 ` Hans de Goede
2022-02-17 11:26 ` Pavel Machek
2022-01-28 9:22 ` [PATCH 1/2] leds: simatic-ipc-leds: Make simatic_ipc_led_mem_res static Henning Schild
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=20220117112109.215695-1-hdegoede@redhat.com \
--to=hdegoede@redhat.com \
--cc=henning.schild@siemens.com \
--cc=linux-leds@vger.kernel.org \
--cc=lkp@intel.com \
--cc=pavel@ucw.cz \
/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