qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 1/2] linux-headers: Update KVM headers from linu


From: Christoffer Dall
Subject: Re: [Qemu-devel] [PATCH 1/2] linux-headers: Update KVM headers from linux-next tag ToBeFilled
Date: Wed, 3 Dec 2014 12:03:24 +0100
User-agent: Mutt/1.5.21 (2010-09-15)

On Wed, Dec 03, 2014 at 11:53:58AM +0100, Eric Auger wrote:
> On 12/03/2014 11:49 AM, Christoffer Dall wrote:
> > 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 <address@hidden>
> > 
> > How can this be from linux-next?  I'm pretty sure we didn't merge this
> > patch yet.
> 
> Hi Christoffer,
> 
> yes that's correct . I don't know how to format that kind of patch that
> refers to linux headers (I mentioned in the title tag ToBeFilled). I
> looked at other similar ones and I thought this was the wording that is
> generally used. I can move it to RFC but it will stay as is until kernel
> patches are upstreamed. In that case I should also move the QEMU VFIO
> patch back to RFC due to forwarding stuff;-)
> 
This patch subject should just be something like this:

Subject: [RFC PATCH 1/2] linux-headers: Update KVM headers for 
KVM_DEV_ARM_VGIC_GRP_CTRL

And in the commit message you point to a personal git tree that contains
the patches you're syncing against.

-Christoffer



reply via email to

[Prev in Thread] Current Thread [Next in Thread]