All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: David Howells <dhowells@redhat.com>
Cc: Andy King <acking@vmware.com>,
	pv-drivers@vmware.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org, davem@davemloft.net
Subject: Re: [PATCH] VSOCK: Split vm_sockets.h into kernel/uapi
Date: Fri, 8 Mar 2013 07:24:53 +0800	[thread overview]
Message-ID: <20130307232453.GD10304@kroah.com> (raw)
In-Reply-To: <26621.1362675490@warthog.procyon.org.uk>

On Thu, Mar 07, 2013 at 04:58:10PM +0000, David Howells wrote:
> Andy King <acking@vmware.com> wrote:
> 
> > Split the vSockets header into kernel and UAPI parts.  The former gets the bits
> > that used to be in __KERNEL__ guards, while the latter gets everything that is
> > user-visible.  Tested by compiling vsock (+transport) and a simple user-mode
> > vSockets application.
> > 
> > Reported-by: David Howells <dhowells@redhat.com>
> > Acked-by: Dmitry Torokhov <dtor@vmware.com>
> > Signed-off-by: Andy King <acking@vmware.com>
> 
> Acked-by: David Howells <dhowells@redhat.com>

David, is there any rush to get stuff like this into 3.9 for any
uapi-type changes, or can it just wait for 3.10?

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: David Howells <dhowells@redhat.com>
Cc: Andy King <acking@vmware.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org, davem@davemloft.net,
	pv-drivers@vmware.com
Subject: Re: [PATCH] VSOCK: Split vm_sockets.h into kernel/uapi
Date: Fri, 8 Mar 2013 07:24:53 +0800	[thread overview]
Message-ID: <20130307232453.GD10304@kroah.com> (raw)
In-Reply-To: <26621.1362675490@warthog.procyon.org.uk>

On Thu, Mar 07, 2013 at 04:58:10PM +0000, David Howells wrote:
> Andy King <acking@vmware.com> wrote:
> 
> > Split the vSockets header into kernel and UAPI parts.  The former gets the bits
> > that used to be in __KERNEL__ guards, while the latter gets everything that is
> > user-visible.  Tested by compiling vsock (+transport) and a simple user-mode
> > vSockets application.
> > 
> > Reported-by: David Howells <dhowells@redhat.com>
> > Acked-by: Dmitry Torokhov <dtor@vmware.com>
> > Signed-off-by: Andy King <acking@vmware.com>
> 
> Acked-by: David Howells <dhowells@redhat.com>

David, is there any rush to get stuff like this into 3.9 for any
uapi-type changes, or can it just wait for 3.10?

thanks,

greg k-h

  reply	other threads:[~2013-03-07 23:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-07 15:26 [PATCH] VSOCK: Split vm_sockets.h into kernel/uapi Andy King
2013-03-07 15:26 ` Andy King
2013-03-07 16:58 ` David Howells
2013-03-07 23:24   ` Greg KH [this message]
2013-03-07 23:24     ` Greg KH
2013-03-08  1:09     ` David Howells
2013-03-08  1:09       ` David Howells
2013-03-08 17:26       ` David Miller
2013-03-08 17:26         ` David Miller
2013-03-07 16:58 ` David Howells

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=20130307232453.GD10304@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=acking@vmware.com \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pv-drivers@vmware.com \
    --cc=virtualization@lists.linux-foundation.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.