linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jisheng Zhang <jszhang@marvell.com>
To: gregkh@linuxfoundation.org, jslaby@suse.com
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jisheng Zhang <jszhang@marvell.com>
Subject: [PATCH] serial: 8250_dw: #ifdef out dw8250_acpi_match if ACPI isn't set
Date: Fri, 23 Dec 2016 20:33:55 +0800	[thread overview]
Message-ID: <20161223123355.1370-1-jszhang@marvell.com> (raw)

dw8250_acpi_match is used only when ACPI is enabled. Fix the following
gcc warning when W=1 is set:

drivers/tty/serial/8250/8250_dw.c:640:36: warning: 'dw8250_acpi_match'
defined but not used [-Wunused-const-variable=]

Signed-off-by: Jisheng Zhang <jszhang@marvell.com>
---
 drivers/tty/serial/8250/8250_dw.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/tty/serial/8250/8250_dw.c b/drivers/tty/serial/8250/8250_dw.c
index c89fafc972b6..bd43cbfd0783 100644
--- a/drivers/tty/serial/8250/8250_dw.c
+++ b/drivers/tty/serial/8250/8250_dw.c
@@ -637,6 +637,7 @@ static const struct of_device_id dw8250_of_match[] = {
 };
 MODULE_DEVICE_TABLE(of, dw8250_of_match);
 
+#ifdef CONFIG_ACPI
 static const struct acpi_device_id dw8250_acpi_match[] = {
 	{ "INT33C4", 0 },
 	{ "INT33C5", 0 },
@@ -651,6 +652,7 @@ static const struct acpi_device_id dw8250_acpi_match[] = {
 	{ },
 };
 MODULE_DEVICE_TABLE(acpi, dw8250_acpi_match);
+#endif
 
 static struct platform_driver dw8250_platform_driver = {
 	.driver = {
-- 
2.11.0

             reply	other threads:[~2016-12-23 12:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-23 12:33 Jisheng Zhang [this message]
2016-12-23 18:09 ` [PATCH] serial: 8250_dw: #ifdef out dw8250_acpi_match if ACPI isn't set Greg KH
2016-12-26  5:28   ` Jisheng Zhang

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=20161223123355.1370-1-jszhang@marvell.com \
    --to=jszhang@marvell.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@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;
as well as URLs for NNTP newsgroup(s).