linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Valentin Rothberg <valentinrothberg@gmail.com>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: linux-next: Tree for Dec 12
Date: Fri, 12 Dec 2014 11:31:56 +0100	[thread overview]
Message-ID: <1418380316.5756.37.camel@x220> (raw)
In-Reply-To: <20141212210449.7f460bb1@canb.auug.org.au>

On Fri, 2014-12-12 at 21:04 +1100, Stephen Rothwell wrote:
> That patch has been in linux-next since Dec 3 as commit 77a4494388ab in
> Andrew's patch set (and maybe earlier).

Not earlier. Commit 77a4494388ab debuted in next-20141203:
        $ git tag --contains 77a4494388ab
        next-20141203
        next-20141204
        next-20141205
        next-20141208
        next-20141209
        next-20141210
        next-20141211
        next-20141212
        
I missed that commit. But then again it never occurred to me that a
Kconfig symbol would be added and removed in one series. And, obviously,
grepping for INIT_FALLBACK didn't show anything in linux-next before
today (the oldest tree I checked was next-20141201, after which I lost
interest in going back any further). 

>   However, also in Adnrew's
> patch set is another patch ("init: remove CONFIG_INIT_FALLBACK") that
> then removes CONFIG_INIT_FALLBACK.  There is a conflict because the
> first has gone into Linus' tree today (as commit 6ef4536e2f19), but the
> second has not (I don't know why not).
> 
> Hmmm, I would have expected the Kconfig entry to be removed as well,
> but either I missed that, or git is not as clever as I expect it to be.
> 
> > Anyhow, I'm sure this all will be sorted out in due time.
> 
> I hope so.

I won't be bothering (Andrew and) you again about this. Unless sorting
this out takes rather long, that is.

Thanks,


Paul Bolle

  reply	other threads:[~2014-12-12 10:31 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 [this message]
2014-12-12 21:57       ` Andrew Morton
2014-12-12 22:36         ` Paul Bolle
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=1418380316.5756.37.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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).