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 17:06:20 -0400 [thread overview]
Message-ID: <20071029210620.GB27547@tuxdriver.com> (raw)
In-Reply-To: <4726497F.2010709@oracle.com>
On Mon, Oct 29, 2007 at 01:58:39PM -0700, Randy Dunlap wrote:
> >Would you mind explaining how changing the name of the pci_driver
> >variable resolves this? There must be some magic here...
>
> Oh, sure. In scripts/mod/modpost.c, there is a whitelist of variable
> name suffixes. Those suffixes are assumed to be safe for referring
> to non-text code/data. OTOH, if someone complains enough, another
> whitelist table element can also be added...
Ah, got it. Thanks!
John
--
John W. Linville
linville@tuxdriver.com
prev parent reply other threads:[~2007-10-29 21:07 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
2007-10-29 20:58 ` Randy Dunlap
2007-10-29 21:06 ` John W. Linville [this message]
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=20071029210620.GB27547@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