From: "Radim Krčmář" <rkrcmar@redhat.com>
To: James Hogan <james.hogan@imgtec.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org, kvm@vger.kernel.org
Subject: Re: [GIT PULL] MIPS KVM fix for v4.9-rc2
Date: Fri, 21 Oct 2016 20:52:29 +0200 [thread overview]
Message-ID: <20161021185228.GA25783@potion> (raw)
In-Reply-To: <20161020192657.GN7370@jhogan-linux.le.imgtec.org>
2016-10-20 20:26+0100, James Hogan:
> What is the queue branch for?
It is a staging branch. All patches applied by Paolo or me usually
start in kvm/queue.
Applying to kvm/queue means that we think that the patch is ok, but it
is by no means final -- the on-list review continues and we add r-b
tags, do minimal changes, or even drop patches according to feedback.
Patches are tested in kvm/queue before being included in a permanent
branch.
prev parent reply other threads:[~2016-10-21 18:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 13:52 [GIT PULL] MIPS KVM fix for v4.9-rc2 James Hogan
2016-10-20 13:52 ` James Hogan
2016-10-20 13:52 ` [GIT PULL] KVM: MIPS: Add missing uaccess.h include James Hogan
2016-10-20 13:52 ` James Hogan
2016-10-20 18:04 ` [GIT PULL] MIPS KVM fix for v4.9-rc2 Radim Krčmář
2016-10-20 19:26 ` James Hogan
2016-10-20 19:26 ` James Hogan
2016-10-21 18:52 ` Radim Krčmář [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=20161021185228.GA25783@potion \
--to=rkrcmar@redhat.com \
--cc=james.hogan@imgtec.com \
--cc=kvm@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=pbonzini@redhat.com \
--cc=ralf@linux-mips.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.