From: Chris Peterson <cpeterso@cpeterso.com>
To: linux-kernel@vger.kernel.org
Subject: const-correctness warnings from gcc -Wwrite-strings?
Date: Mon, 4 May 2009 17:00:59 -0700 [thread overview]
Message-ID: <a24804730905041700i66418576q7b146b05e78884d3@mail.gmail.com> (raw)
I am preparing a patch that would fix some const-correctness warnings
when compiling the kernel with gcc -Wwrite-strings. I am not (yet?)
proposing that the kernel Makefile should use -Wwrite-strings.
String constants are not writable, but without -Wwrite-strings, gcc
pretends string constants have type non-const char[] to support lazy
legacy code. :)
Are these fixes of any interest? The only controversy I see is that
some of the changes affect the function signatures of some ops
structures' function pointers.
chris
next reply other threads:[~2009-05-05 0:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 0:00 Chris Peterson [this message]
2009-05-05 2:47 ` Valdis.Kletnieks
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=a24804730905041700i66418576q7b146b05e78884d3@mail.gmail.com \
--to=cpeterso@cpeterso.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®