From: Floris Kraak <randakar@gmail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Robert Hancock <hancockrwd@gmail.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Trivial Patch Monkey <trivial@kernel.org>,
Roland Dreier <rdreier@cisco.com>
Subject: Re: [PATCH] Kbuild: Enable the gcc flag -Wformat-security (was: Re: [PATCH] Kbuild: Disable the -Wformat-security gcc flag)
Date: Thu, 5 Feb 2009 21:10:02 +0100 [thread overview]
Message-ID: <56e1b5710902051210o75401c75nfc3797c2465897fb@mail.gmail.com> (raw)
In-Reply-To: <20090205195459.GB2617@uranus.ravnborg.org>
On Thu, Feb 5, 2009 at 8:54 PM, Sam Ravnborg <sam@ravnborg.org> wrote:
> On Thu, Feb 05, 2009 at 09:57:28AM +0100, Floris Kraak wrote:
>> On Thu, Feb 5, 2009 at 9:47 AM, Floris Kraak <randakar@gmail.com> wrote:
>>
>> Resend, seems like the earlier patch doesn't quite actually work as
>> advertised; -Wformat-security needs -Wformat enabled as well.
>> ---
>> [PATCH] Kbuild: Enable the gcc flag -Wformat-security
>
> We need to sort out the ~150 warnings you see in your
> allyesconfig build before applying this one.
> We try to avoid applying patches that increases the warning count
> without some effort done to fix it first.
>
> So let see what the other patch end up with.
>
Fine with me, the other patch needs to cook a bit first tho ;-)
Regards,
Floris
---
"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety."
-- Ben Franklin
"The course of history shows that as a government grows, liberty
decreases."
-- Thomas Jefferson
prev parent reply other threads:[~2009-02-05 20:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 8:47 Floris Kraak
2009-02-05 8:57 ` Floris Kraak
2009-02-05 19:54 ` Sam Ravnborg
2009-02-05 20:10 ` Floris Kraak [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=56e1b5710902051210o75401c75nfc3797c2465897fb@mail.gmail.com \
--to=randakar@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hancockrwd@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdreier@cisco.com \
--cc=sam@ravnborg.org \
--cc=trivial@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®