From: Stephen Hemminger <shemminger@vyatta.com>
To: Joe Perches <joe@perches.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH] atlx: make strings const
Date: Wed, 8 Sep 2010 18:54:14 -0700 [thread overview]
Message-ID: <20100908185414.52f6f35a@nehalam> (raw)
In-Reply-To: <1283986691.24986.31.camel@Joe-Laptop>
On Wed, 08 Sep 2010 15:58:11 -0700
Joe Perches <joe@perches.com> wrote:
> On Wed, 2010-09-08 at 15:18 -0700, Stephen Hemminger wrote:
> > Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>
> > Acked-by: Chris Snook <chris.snook@gmail.com>
> >
>
> Shouldn't that be done with all of the global
> static char foo[] = "bar"; declarations?
Yes, that what I was looking at when I found some of these.
Those that are __initdata don't matter as much since they
get dropped (although they could be changed to __initconst).
next prev parent reply other threads:[~2010-09-09 1:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 22:18 [PATCH] atlx: make strings const Stephen Hemminger
2010-09-08 22:58 ` Joe Perches
2010-09-09 1:54 ` Stephen Hemminger [this message]
2010-09-09 4:32 ` David Miller
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=20100908185414.52f6f35a@nehalam \
--to=shemminger@vyatta.com \
--cc=davem@davemloft.net \
--cc=joe@perches.com \
--cc=netdev@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).