From: Ivo van Doorn <ivdoorn@gmail.com>
To: Helmut Schaa <helmut.schaa@googlemail.com>
Cc: John Linville <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org,
Gertjan van Wingerde <gwingerde@gmail.com>
Subject: Re: [PATCH] rt2x00: fix warning when building rt2800pci with just soc support
Date: Mon, 15 Mar 2010 17:35:46 +0100 [thread overview]
Message-ID: <201003151735.46646.IvDoorn@gmail.com> (raw)
In-Reply-To: <201003151722.26406.helmut.schaa@googlemail.com>
On Monday 15 March 2010, Helmut Schaa wrote:
> Fix compile warning "rt2800pci.c:1248: warning: 'rt2800pci_device_table'
> defined but not used" when building rt2800pci with only soc support
> (without pci).
>
> Signed-off-by: Helmut Schaa <helmut.schaa@googlemail.com>
Acked-by: Ivo van Doorn <IvDoorn@gmail.com>
> ---
> Nothing important, had the patch in my tree and just noticed that I didn't
> send it out yet.
>
> drivers/net/wireless/rt2x00/rt2800pci.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/net/wireless/rt2x00/rt2800pci.c b/drivers/net/wireless/rt2x00/rt2800pci.c
> index 10fafd0..0104906 100644
> --- a/drivers/net/wireless/rt2x00/rt2800pci.c
> +++ b/drivers/net/wireless/rt2x00/rt2800pci.c
> @@ -1184,6 +1184,7 @@ static const struct rt2x00_ops rt2800pci_ops = {
> /*
> * RT2800pci module information.
> */
> +#ifdef CONFIG_RT2800PCI_PCI
> static DEFINE_PCI_DEVICE_TABLE(rt2800pci_device_table) = {
> { PCI_DEVICE(0x1814, 0x0601), PCI_DEVICE_DATA(&rt2800pci_ops) },
> { PCI_DEVICE(0x1814, 0x0681), PCI_DEVICE_DATA(&rt2800pci_ops) },
> @@ -1211,6 +1212,7 @@ static DEFINE_PCI_DEVICE_TABLE(rt2800pci_device_table) = {
> #endif
> { 0, }
> };
> +#endif /* CONFIG_RT2800PCI_PCI */
>
> MODULE_AUTHOR(DRV_PROJECT);
> MODULE_VERSION(DRV_VERSION);
next prev parent reply other threads:[~2010-03-15 16:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 16:22 [PATCH] rt2x00: fix warning when building rt2800pci with just soc support Helmut Schaa
2010-03-15 16:35 ` Ivo van Doorn [this message]
2010-03-15 19:08 ` Gertjan van Wingerde
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=201003151735.46646.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=gwingerde@gmail.com \
--cc=helmut.schaa@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).