From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Borislav Petkov <bp@alien8.de>,
Andrew Morton <akpm@linux-foundation.org>,
Andreas Mohr <andi@lisas.de>,
linux-kernel@vger.kernel.org, Li Shaohua <shaohua.li@intel.com>,
linux-acpi@vger.kernel.org
Subject: Re: Look Ma, da kernel is b0rken
Date: Thu, 6 Dec 2012 07:57:21 +1100 [thread overview]
Message-ID: <20121206075721.18c0c05aa767b330f47d77eb@canb.auug.org.au> (raw)
In-Reply-To: <20121205154749.2af4ef36@pyramind.ukuu.org.uk>
[-- Attachment #1: Type: text/plain, Size: 816 bytes --]
Hi Alan,
On Wed, 5 Dec 2012 15:47:49 +0000 Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>
> And yes btw we should turn this option on in -next, and get these sort of
> things out of the tree for good. More importantly it'll mean anyone
> adding another one gets a whine on the spot.
While I appreciate your confidence, I don't notice quite a few new
warnings (because there are so many of them already :-(). Is there some
reason to not turn this on in our "normal" builds? Does it produce many
false positives? What compiler version is required?
I also currently don't carry patches that only ever appear in linux-next
(well, not intentionally anyway). I assume it would require a patch to
the Makefile(s) to turn this on.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-12-05 20:57 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 7:09 Look Ma, da kernel is b0rken Andreas Mohr
2012-12-05 14:29 ` Borislav Petkov
2012-12-05 15:27 ` Alan Cox
2012-12-05 15:31 ` Borislav Petkov
2012-12-05 15:47 ` Alan Cox
2012-12-05 15:59 ` Borislav Petkov
2012-12-05 17:04 ` Geert Uytterhoeven
2012-12-05 17:37 ` Borislav Petkov
2012-12-05 20:57 ` Stephen Rothwell [this message]
2012-12-05 21:12 ` Borislav Petkov
2012-12-05 21:41 ` Alan Cox
2012-12-05 21:46 ` Borislav Petkov
2012-12-05 21:39 ` Alan Cox
2012-12-05 21:38 ` Andrew Morton
2012-12-05 21:50 ` Borislav Petkov
2012-12-07 16:52 ` Andreas Mohr
2012-12-07 17:44 ` Borislav Petkov
2012-12-08 7:36 ` Andreas Mohr
2012-12-08 10:52 ` Borislav Petkov
2012-12-08 23:04 ` Alan Cox
2012-12-05 16:39 ` Andreas Mohr
2012-12-05 16:44 ` Borislav Petkov
2012-12-05 17:09 ` Andreas Mohr
2012-12-05 17:34 ` Borislav Petkov
2012-12-05 23:38 ` Rafael J. Wysocki
2012-12-05 23:35 ` Borislav Petkov
2012-12-06 14:04 ` Alan Cox
2012-12-06 20:56 ` Rafael J. Wysocki
2012-12-06 20:59 ` Borislav Petkov
2012-12-06 21:21 ` Rafael J. Wysocki
2012-12-06 21:20 ` Borislav Petkov
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=20121206075721.18c0c05aa767b330f47d77eb@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andi@lisas.de \
--cc=bp@alien8.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.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;
as well as URLs for NNTP newsgroup(s).