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: Thu, 20 Oct 2016 20:04:50 +0200 [thread overview]
Message-ID: <20161020180449.GC8569@potion> (raw)
In-Reply-To: <1476971554-1215-1-git-send-email-james.hogan@imgtec.com>
2016-10-20 14:52+0100, James Hogan:
> Hi Radim, Paolo,
>
> The following changes since commit 1001354ca34179f3db924eb66672442a173147dc:
>
> Linux 4.9-rc1 (2016-10-15 12:17:50 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jhogan/kvm-mips.git tags/kvm_mips_4.9_2
>
> for you to fetch changes up to d852b5f35e84e60c930589eeb14a6df21ea9b1cb:
>
> KVM: MIPS: Add missing uaccess.h include (2016-10-19 00:37:05 +0100)
>
> I'd already based this on v4.9-rc1 rather than the kvm next branch which
> isn't up to v4.9-rc1 yet. If thats a problem I can easily rebase, or
> feel free to apply the patch directly.
Not a problem, I would have done that anyway.
Pulled, thanks.
Btw. patches for -rc2+ kernels ought to be based on kvm/master.
It doesn't matter now, but kvm/master and kvm/next will diverge at -rc3
(max 4), when patches intended for 4.10 are going to be applied to
kvm/next. And kvm/next isn't rebased, so it will stay on -rc[34] until
Linus pulls in the 4.10 merge window.
next prev parent reply other threads:[~2016-10-20 18:04 UTC|newest]
Thread overview: 5+ 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 ` [GIT PULL] KVM: MIPS: Add missing uaccess.h include James Hogan
2016-10-20 18:04 ` Radim Krčmář [this message]
2016-10-20 19:26 ` [GIT PULL] MIPS KVM fix for v4.9-rc2 James Hogan
2016-10-21 18:52 ` Radim Krčmář
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=20161020180449.GC8569@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).