From: Michael Ellerman <michael@ellerman•id.au>
To: Pekka Enberg <penberg@kernel•org>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Sasha Levin <levinsasha928@gmail•com>,
Thomas Gleixner <tglx@linutronix•de>, Ingo Molnar <mingo@elte•hu>,
"H. Peter Anvin" <hpa@zytor•com>,
Peter Zijlstra <peterz@infradead•org>,
linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
Linus <torvalds@linux-foundation•org>,
Andrew Morton <akpm@linux-foundation•org>
Subject: Re: linux-next: fate of the kvmtool tree
Date: Wed, 03 Oct 2012 18:22:31 +1000 [thread overview]
Message-ID: <1349252551.31536.29.camel@concordia> (raw)
In-Reply-To: <CAOJsxLFeVa6WCpr25t3hA3xGJb6rUgFqOLDrc5_3iLnUb-xTHw@mail.gmail.com>
On Wed, 2012-10-03 at 09:47 +0300, Pekka Enberg wrote:
> Hi Stephen,
>
> On Wed, Oct 3, 2012 at 8:29 AM, Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> > Well, here we are at another merge window and the kvmtool tree is still
> > not merged. So, is it likely that it will be merged in this merge
> > window? or the next? If not, can I please remove it from linux-next
> > (and have it removed from the auto-latest branch of the tip tree) as it
> > just adds weight to the patches and the tree that people have to fetch to
> > work with.
>
> I have no idea how likely it is that it will be merged but I'm
> planning to send a pull request for this merge cycle. ;-)
Hi Pekka,
I just noticed kvmtool doesn't build for powerpc anymore, since 8074303
"remove global kvm object".
It'd be nice if it wasn't broken when it hit Linus' tree, I'll try and
get you a patch in the next day.
cheers
prev parent reply other threads:[~2012-10-03 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 5:29 linux-next: fate of the kvmtool tree Stephen Rothwell
2012-10-03 6:47 ` Pekka Enberg
2012-10-03 8:22 ` Michael Ellerman [this message]
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=1349252551.31536.29.camel@concordia \
--to=michael@ellerman$(echo .)id.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=hpa@zytor$(echo .)com \
--cc=levinsasha928@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
--cc=penberg@kernel$(echo .)org \
--cc=peterz@infradead$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tglx@linutronix$(echo .)de \
--cc=torvalds@linux-foundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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