From: Marcelo Tosatti <mtosatti@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Paul Mackerras <paulus@samba.org>, Avi Kivity <avi@redhat.com>,
kvm-ppc@vger.kernel.org, KVM list <kvm@vger.kernel.org>
Subject: Re: [PATCH] KVM: Move some PPC ioctl definitions to the correct place
Date: Sat, 15 Sep 2012 15:40:29 +0000 [thread overview]
Message-ID: <20120915154029.GD3037@amt.cnet> (raw)
In-Reply-To: <AB10A801-905C-4C9C-9F60-C5E620BB3878@suse.de>
On Fri, Sep 14, 2012 at 04:19:29PM +0200, Alexander Graf wrote:
>
> On 14.09.2012, at 09:44, Paul Mackerras wrote:
>
> > This moves the definitions of KVM_CREATE_SPAPR_TCE and
> > KVM_ALLOCATE_RMA in include/linux/kvm.h from the section listing the
> > vcpu ioctls to the section listing VM ioctls, as these are both
> > implemented and documented as VM ioctls.
> >
> > Fortunately there is no actual collision of ioctl numbers at this
> > point. Moving these to the correct section will reduce the
> > probability of a future collision. This does not change the
> > user/kernel ABI at all.
> >
> > Signed-off-by: Paul Mackerras <paulus@samba.org>
>
> Acked-by: Alexander Graf <agraf@suse.de>
>
>
> Avi / Marcelo, please pull this in directly.
>
> Alex
Can you please bounce it to me? I deleted on the basis it would be
integrated through kvm-ppc tree.
WARNING: multiple messages have this Message-ID (diff)
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Paul Mackerras <paulus@samba.org>, Avi Kivity <avi@redhat.com>,
kvm-ppc@vger.kernel.org, KVM list <kvm@vger.kernel.org>
Subject: Re: [PATCH] KVM: Move some PPC ioctl definitions to the correct place
Date: Sat, 15 Sep 2012 12:40:29 -0300 [thread overview]
Message-ID: <20120915154029.GD3037@amt.cnet> (raw)
In-Reply-To: <AB10A801-905C-4C9C-9F60-C5E620BB3878@suse.de>
On Fri, Sep 14, 2012 at 04:19:29PM +0200, Alexander Graf wrote:
>
> On 14.09.2012, at 09:44, Paul Mackerras wrote:
>
> > This moves the definitions of KVM_CREATE_SPAPR_TCE and
> > KVM_ALLOCATE_RMA in include/linux/kvm.h from the section listing the
> > vcpu ioctls to the section listing VM ioctls, as these are both
> > implemented and documented as VM ioctls.
> >
> > Fortunately there is no actual collision of ioctl numbers at this
> > point. Moving these to the correct section will reduce the
> > probability of a future collision. This does not change the
> > user/kernel ABI at all.
> >
> > Signed-off-by: Paul Mackerras <paulus@samba.org>
>
> Acked-by: Alexander Graf <agraf@suse.de>
>
>
> Avi / Marcelo, please pull this in directly.
>
> Alex
Can you please bounce it to me? I deleted on the basis it would be
integrated through kvm-ppc tree.
next prev parent reply other threads:[~2012-09-15 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 7:44 [PATCH] KVM: Move some PPC ioctl definitions to the correct place Paul Mackerras
2012-09-14 7:44 ` Paul Mackerras
2012-09-14 14:19 ` Alexander Graf
2012-09-14 14:19 ` Alexander Graf
2012-09-15 15:40 ` Marcelo Tosatti [this message]
2012-09-15 15:40 ` Marcelo Tosatti
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=20120915154029.GD3037@amt.cnet \
--to=mtosatti@redhat.com \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=paulus@samba.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.