From: "John W. Linville" <linville@tuxdriver.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-wireless@vger.kernel.org, j@w1.fi,
akpm <akpm@linux-foundation.org>
Subject: Re: [PATCH] hostap: fix section mismatch warning
Date: Mon, 29 Oct 2007 16:52:54 -0400 [thread overview]
Message-ID: <20071029205254.GA27547@tuxdriver.com> (raw)
In-Reply-To: <20071029112026.f66473c5.randy.dunlap@oracle.com>
On Mon, Oct 29, 2007 at 11:20:26AM -0700, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> Fix section mismatch warning:
>
> WARNING: vmlinux.o(.data+0x36fcc): Section mismatch: reference to .init.data:prism2_pci_id_table (between 'prism2_pci_drv_id' and 'prism2_pci_funcs')
>
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> ---
> drivers/net/wireless/hostap/hostap_pci.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> --- linux-2624-rc1g4-v1.orig/drivers/net/wireless/hostap/hostap_pci.c
> +++ linux-2624-rc1g4-v1/drivers/net/wireless/hostap/hostap_pci.c
> @@ -444,7 +444,7 @@ static int prism2_pci_resume(struct pci_
>
> MODULE_DEVICE_TABLE(pci, prism2_pci_id_table);
>
> -static struct pci_driver prism2_pci_drv_id = {
> +static struct pci_driver prism2_pci_driver = {
> .name = "hostap_pci",
> .id_table = prism2_pci_id_table,
> .probe = prism2_pci_probe,
Randy,
Would you mind explaining how changing the name of the pci_driver
variable resolves this? There must be some magic here...
Thanks!
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2007-10-29 20:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 18:20 [PATCH] hostap: fix section mismatch warning Randy Dunlap
2007-10-29 20:52 ` John W. Linville [this message]
2007-10-29 20:58 ` Randy Dunlap
2007-10-29 21:06 ` John W. Linville
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=20071029205254.GA27547@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=akpm@linux-foundation.org \
--cc=j@w1.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=randy.dunlap@oracle.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