From: Christoffer Dall <christoffer.dall@linaro.org>
To: Eric Auger <eric.auger@linaro.org>
Cc: peter.maydell@linaro.org, eric.auger@st.com,
ard.biesheuvel@linaro.org, marc.zyngier@arm.com,
patches@linaro.org, agraf@suse.de, qemu-devel@nongnu.org,
alex.williamson@redhat.com, kvmarm@lists.cs.columbia.edu,
a.motakis@virtualopensystems.com, pbonzini@redhat.com,
afaerber@suse.de, a.rigo@virtualopensystems.com
Subject: Re: [Qemu-devel] [PATCH 1/2] linux-headers: Update KVM headers from linux-next tag ToBeFilled
Date: Wed, 3 Dec 2014 11:49:28 +0100 [thread overview]
Message-ID: <20141203104928.GF17502@cbox> (raw)
In-Reply-To: <1417544894-2000-2-git-send-email-eric.auger@linaro.org>
On Tue, Dec 02, 2014 at 06:28:13PM +0000, Eric Auger wrote:
> Syncup KVM related linux headers from linux-next tree using
> scripts/update-linux-headers.sh.
>
> Add a new group/attribute in VGIC KVM device enabling to force
> vgic init: KVM_DEV_ARM_VGIC_GRP_CTRL/KVM_DEV_ARM_VGIC_CTRL_INIT
>
> Signed-off-by: Eric Auger <eric.auger@linaro.org>
How can this be from linux-next? I'm pretty sure we didn't merge this
patch yet.
Also, if you synced your headers from your local tree, I think that
generally makes such a QEMU patches series an RFC one.
-Christoffer
next prev parent reply other threads:[~2014-12-03 10:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 18:28 [Qemu-devel] [PATCH 0/2] arm_gic: Initialize VGIC on machine init done Eric Auger
2014-12-02 18:28 ` [Qemu-devel] [PATCH 1/2] linux-headers: Update KVM headers from linux-next tag ToBeFilled Eric Auger
2014-12-03 10:49 ` Christoffer Dall [this message]
2014-12-03 10:53 ` Eric Auger
2014-12-03 11:03 ` Christoffer Dall
2014-12-03 11:03 ` Eric Auger
2014-12-02 18:28 ` [Qemu-devel] [PATCH 2/2] hw/intc/arm_gic: Initialize the vgic on machine init done Eric Auger
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=20141203104928.GF17502@cbox \
--to=christoffer.dall@linaro.org \
--cc=a.motakis@virtualopensystems.com \
--cc=a.rigo@virtualopensystems.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=alex.williamson@redhat.com \
--cc=ard.biesheuvel@linaro.org \
--cc=eric.auger@linaro.org \
--cc=eric.auger@st.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.com \
--cc=patches@linaro.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).