All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Pekka Enberg <penberg@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@kernel.org>, Avi Kivity <avi@redhat.com>,
	linux-kernel@vger.kernel.org,
	Christoph Hellwig <hch@infradead.org>
Subject: Re: [GIT PULL] Linux KVM tool for v3.7-rc0
Date: Tue, 16 Oct 2012 13:41:29 +1100	[thread overview]
Message-ID: <20121016134129.2fcd7c8ebe1235065aea929e@canb.auug.org.au> (raw)
In-Reply-To: <alpine.LFD.2.02.1210121434140.10531@tux.localdomain>

[-- Attachment #1: Type: text/plain, Size: 555 bytes --]

Hi Linus,

On Fri, 12 Oct 2012 14:34:33 +0300 (EEST) Pekka Enberg <penberg@kernel.org> wrote:
>
> Please consider pulling the latest LKVM tree from:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/penberg/linux.git kvmtool/for-linus

So you have not taken this in the v3.7 merge window.

Will you ever merge this?   If not, it should be removed from linux-next
(where it has been sitting since before v3.1) and turned into an
independent (to the kernel) project.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2012-10-16  2:41 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-12 11:34 [GIT PULL] Linux KVM tool for v3.7-rc0 Pekka Enberg
2012-10-12 17:27 ` Christoph Hellwig
2012-10-18 10:03   ` Ingo Molnar
2012-10-18 10:31     ` Pekka Enberg
2012-10-16  2:41 ` Stephen Rothwell [this message]
2012-10-16 14:50   ` Linus Torvalds
2012-10-20  7:04     ` Stephen Rothwell
2012-10-20 18:14       ` Borislav Petkov
2012-10-21  3:07         ` Dave Airlie
2012-10-21  3:46           ` Yinghai Lu
2012-10-21 11:03           ` Christoph Hellwig
2012-10-21 12:59             ` Ingo Molnar
2012-10-21 14:02               ` richard -rw- weinberger
2012-10-21 15:03                 ` Ingo Molnar
2012-10-21 17:15                   ` Borislav Petkov
2012-10-21 17:40                     ` Markus Trippelsdorf
2012-10-21 17:51                       ` Ingo Molnar
2012-10-21 17:54                         ` Markus Trippelsdorf
2012-10-21 18:04                           ` Markus Trippelsdorf
2012-10-21 18:10                             ` Ingo Molnar
2012-10-22  9:26                               ` Avi Kivity
2012-10-21 18:09                           ` Ingo Molnar
2012-10-21 15:39                 ` Pekka Enberg
2012-10-22  9:24                   ` Avi Kivity
2012-10-22 10:16                     ` Gleb Natapov
2012-10-23  2:20                       ` Asias He
2012-10-31 15:05                         ` Gleb Natapov
2012-10-21 11:18           ` Borislav Petkov
2012-10-21 11:29             ` richard -rw- weinberger
2012-10-21 22:16               ` Theodore Ts'o
2012-11-14  5:24       ` Stephen Rothwell
2012-11-14  6:02         ` Theodore Ts'o

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=20121016134129.2fcd7c8ebe1235065aea929e@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=akpm@linux-foundation.org \
    --cc=avi@redhat.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=penberg@kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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.