From: Andi Kleen <ak@linux.intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Michal Marek <mmarek@suse.cz>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: clean up the kbuild tree?
Date: Sun, 15 Nov 2015 09:58:48 -0800 [thread overview]
Message-ID: <20151115175848.GD10150@tassilo.jf.intel.com> (raw)
In-Reply-To: <20151115112705.0bf4f0ed@canb.auug.org.au>
On Sun, Nov 15, 2015 at 11:27:05AM +1100, Stephen Rothwell wrote:
> Hi Michal,
>
> I notice that the kbuild tree (relative to Linus' tree) only contains
> lots of merges and these 2 commits from April 2014:
Really should get in that patch officially. I have a variety of users.
And it clearly has been tested long enough in linux-next :)
Michal, enough to just repost it?
-Andi
next prev parent reply other threads:[~2015-11-15 17:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-15 0:27 linux-next: clean up the kbuild tree? Stephen Rothwell
2015-11-15 17:58 ` Andi Kleen [this message]
2015-11-16 13:01 ` Michal Marek
2015-11-21 1:00 ` Andi Kleen
2015-11-21 10:55 ` Takashi Iwai
2015-11-24 2:12 ` Andi Kleen
2015-11-24 16:33 ` LTO build errors (Re: linux-next: clean up the kbuild tree?) Takashi Iwai
2015-11-25 4:33 ` Andi Kleen
2015-11-25 6:58 ` Takashi Iwai
2015-11-30 17:46 ` Andi Kleen
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=20151115175848.GD10150@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.