From: "Radim Krčmář" <rkrcmar@redhat.com>
To: James Hogan <james.hogan@imgtec.com>
Cc: James Cowgill <James.Cowgill@imgtec.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org, kvm@vger.kernel.org
Subject: Re: [PATCH v2] KVM: MIPS: Fix maybe-uninitialized build failure
Date: Tue, 20 Jun 2017 17:07:57 +0200 [thread overview]
Message-ID: <20170620150756.GE10325@potion> (raw)
In-Reply-To: <20170620145432.GV6973@jhogan-linux.le.imgtec.org>
2017-06-20 15:54+0100, James Hogan:
> Acked-by: James Hogan <james.hogan@imgtec.com>
>
> Paolo / Radim: is it okay for one of you to pick this one up for 4.12?
It's in, thanks!
prev parent reply other threads:[~2017-06-20 15:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 9:57 [PATCH v2] KVM: MIPS: Fix maybe-uninitialized build failure James Cowgill
2017-06-20 14:54 ` James Hogan
2017-06-20 15:07 ` 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=20170620150756.GE10325@potion \
--to=rkrcmar@redhat.com \
--cc=James.Cowgill@imgtec.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).