linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Thiago Macieira <thiago.macieira@intel.com>,
	Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kbuild <linux-kbuild@vger.kernel.org>,
	Boris Barbulovski <bbarbulovski@gmail.com>
Subject: Re: linux-next: Tree for Nov 1 (xconfig problem)
Date: Mon, 2 Nov 2015 21:42:41 +0100	[thread overview]
Message-ID: <5637CAC1.6030509@suse.cz> (raw)
In-Reply-To: <1738577.5l9eGhcZuP@tjmaciei-mobl4>

Dne 2.11.2015 v 20:23 Thiago Macieira napsal(a):
> On Monday 02 November 2015 10:48:00 Randy Dunlap wrote:
>> Hi,
>> What does this patch apply to?
>> I can't apply it cleanly to to 4.3 or linux-next of yesterday or today.
> 
> Hmm... interesting, it doesn't apply on linux-next. The reason for that is 
> that the code on linux-next is different from the one on the tip of the branch 
> that I sent to Michal. The difference explains the crash too and why I thought 
> it was impossible.
> 
> Michal, looks like you missed applying patch #28 "Add current selection 
> check." from the original series. It's one of three commits that don't start 
> with "Port xconfig to Qt5", so I guess it was  missed. It's the only commit 
> missing (you applied 38 and the series had 39).
> 
> http://www.spinics.net/lists/linux-kbuild/msg11665.html

Damn, I guess I forgot to select this patch in mutt and the rest applied
without conflicts :-/. Thanks for spotting it, I will add the missing patch.

Michal

  reply	other threads:[~2015-11-02 20:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-01 16:53 linux-next: Tree for Nov 1 Stephen Rothwell
2015-11-02  1:16 ` linux-next: Tree for Nov 1 (lightnvm) Randy Dunlap
2015-11-02 12:43   ` Matias Bjorling
2015-11-02 15:37     ` Jens Axboe
2015-11-02 22:34       ` Matias Bjorling
2015-11-03 16:53         ` Jens Axboe
2015-11-02  3:11 ` linux-next: Tree for Nov 1 (xconfig problem) Randy Dunlap
2015-11-02 13:39   ` Michal Marek
2015-11-02 13:51     ` Thiago Macieira
2015-11-02 16:44       ` Randy Dunlap
2015-11-02 16:58         ` Thiago Macieira
2015-11-02 18:48           ` Randy Dunlap
2015-11-02 19:23             ` Thiago Macieira
2015-11-02 20:42               ` Michal Marek [this message]
2015-11-02 16:01     ` Randy Dunlap
2015-11-02  8:04 ` linux-next: Tree for Nov 1 Geert Uytterhoeven

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=5637CAC1.6030509@suse.cz \
    --to=mmarek@suse.cz \
    --cc=bbarbulovski@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=thiago.macieira@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).