From: Paolo Bonzini <pbonzini@redhat.com>
To: James Hogan <james.hogan@imgtec.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Gleb Natapov <gleb@kernel.org>,
linux-mips@linux-mips.org, kvm@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH 0/3] MIPS: KVM: Misc fixes
Date: Wed, 11 Nov 2015 15:59:39 +0100 [thread overview]
Message-ID: <564357DB.9000904@redhat.com> (raw)
In-Reply-To: <20151111145712.GX26383@jhogan-linux.le.imgtec.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 11/11/2015 15:57, James Hogan wrote:
> Okay, no problem. As long as they can make v4.4.
>
> For the record do you prefer not to receive patches during merge
> window?
It's okay, at worst I won't process them for a few days or weeks.
Paolo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJWQ1fWAAoJEL/70l94x66D5mEIAJbKuP0oRsfMVhZGDlonqzOp
+ugEDNWAzC8tQas2joei0tBtmsFMKY+9NXbFUUthcE0Tn4TbfBi5rRpOfE7B+ekV
Y6sec+vp0AsplpQtNI3OdU8jrZqMYkWUK6ZBdOJrpdPzBzfmFkXuMdimLomhdlVl
8r6Vh6la7RohEJWxXBAaGEzgGqIQ25H+Xw/FNHo3Pk2ZPhI2EgusSlMby6w087kQ
nht5LSVn92Jvx7CNCsqAEhccO/a6XYiRXfW+nFCa/Z1DUvYoezgyXl7jWvyGwKj5
9y73jwIYop63B+KcEDTWZ6gKu2GDrT+TQod+IlWoWDk58PdQjxI1BNcqS+QMFlc=
=VHcV
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2015-11-11 14:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 14:21 [PATCH 0/3] MIPS: KVM: Misc fixes James Hogan
2015-11-11 14:21 ` James Hogan
2015-11-11 14:21 ` [PATCH 1/3] MIPS: KVM: Fix ASID restoration logic James Hogan
2015-11-11 14:21 ` James Hogan
2015-11-11 14:21 ` [PATCH 2/3] MIPS: KVM: Fix CACHE immediate offset sign extension James Hogan
2015-11-11 14:21 ` James Hogan
2015-11-11 14:21 ` [PATCH 3/3] MIPS: KVM: Uninit VCPU in vcpu_create error path James Hogan
2015-11-11 14:21 ` James Hogan
2015-11-11 14:43 ` [PATCH 0/3] MIPS: KVM: Misc fixes Paolo Bonzini
2015-11-11 14:57 ` James Hogan
2015-11-11 14:57 ` James Hogan
2015-11-11 14:59 ` Paolo Bonzini [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=564357DB.9000904@redhat.com \
--to=pbonzini@redhat.com \
--cc=gleb@kernel.org \
--cc=james.hogan@imgtec.com \
--cc=kvm@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=stable@vger.kernel.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.