From: Paul Bolle <pebolle@tiscali.nl>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Valentin Rothberg <valentinrothberg@gmail.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Andy Lutomirski <luto@amacapital.net>,
Josh Triplett <josh@joshtriplett.org>
Subject: Re: linux-next: Tree for Dec 12
Date: Fri, 12 Dec 2014 23:36:37 +0100 [thread overview]
Message-ID: <1418423797.5756.54.camel@x220> (raw)
In-Reply-To: <20141212135719.4c79bac46d43bfd8d7c8e6a6@linux-foundation.org>
On Fri, 2014-12-12 at 13:57 -0800, Andrew Morton wrote:
> On Fri, 12 Dec 2014 11:31:56 +0100 Paul Bolle <pebolle@tiscali.nl> wrote:
> > I won't be bothering (Andrew and) you again about this. Unless sorting
> > this out takes rather long, that is.
>
> Is there some problem with the current mainline 3.19 code?
The problem I noticed is with next-20141212. For some reason - Stephen
appears to not know exactly why - it ended up with a Kconfig entry for
INIT_FALLBACK without any actually users of that Kconfig symbol. My
infamous 800 line perl monster - which I run on every linux-next release
to check for exactly stuff like this - can't help but notice that. The
idea being that my script notices these problems before they actually
hit mainline.
Note that the set of people actually worrying about this stuff contains
me and, maybe, one or two other persons.
Paul Bolle
next prev parent reply other threads:[~2014-12-12 22:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 7:35 linux-next: Tree for Dec 12 Stephen Rothwell
2014-12-12 9:49 ` Paul Bolle
2014-12-12 10:04 ` Stephen Rothwell
2014-12-12 10:31 ` Paul Bolle
2014-12-12 21:57 ` Andrew Morton
2014-12-12 22:36 ` Paul Bolle [this message]
2014-12-12 22:56 ` Andrew Morton
2014-12-13 4:10 ` Stephen Rothwell
2014-12-12 19:00 ` linux-next: Tree for Dec 12 (sound/soc/codecs/rt5640) Randy Dunlap
2014-12-12 21:15 ` linux-next: Tree for Dec 12 (net/bridge) Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2023-12-12 3:32 linux-next: Tree for Dec 12 Stephen Rothwell
2023-12-12 6:25 ` Stephen Rothwell
2019-12-12 4:50 Stephen Rothwell
2018-12-12 6:32 Stephen Rothwell
2017-12-12 5:29 Stephen Rothwell
2016-12-12 6:39 Stephen Rothwell
2013-12-12 6:06 Stephen Rothwell
2011-12-12 5:14 Stephen Rothwell
2011-12-12 21:26 ` Konrad Rzeszutek Wilk
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=1418423797.5756.54.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=akpm@linux-foundation.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=sfr@canb.auug.org.au \
--cc=valentinrothberg@gmail.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).