From: Stephen Hemminger <shemminger@vyatta.com>
To: Joe Perches <joe@perches.com>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
linux-pci <linux-pci@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] include/linux/pci.h: Make struct pci_driver.name const char *
Date: Thu, 9 Sep 2010 07:54:55 -0700 [thread overview]
Message-ID: <20100909075455.0cf3d3a5@nehalam> (raw)
In-Reply-To: <1284017884.24986.93.camel@Joe-Laptop>
On Thu, 09 Sep 2010 00:38:04 -0700
Joe Perches <joe@perches.com> wrote:
> As far as I can tell, name is never modified.
>
> This would allow names to be assigned
> from variables in non-writable sections.
>
> static const foo[] = "bar";
>
> struct pci_driver baz = {
> .name = foo;
> };
>
> Signed-off-by: Joe Perches <joe@perches.com>
> ---
I already sent same patch to Jesse
next prev parent reply other threads:[~2010-09-09 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-09 7:38 [PATCH] include/linux/pci.h: Make struct pci_driver.name const char * Joe Perches
2010-09-09 14:54 ` Stephen Hemminger [this message]
2010-09-09 15:23 ` Joe Perches
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=20100909075455.0cf3d3a5@nehalam \
--to=shemminger@vyatta.com \
--cc=jbarnes@virtuousgeek.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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