[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20121130211740.GA1131@kroah.com>
Date: Fri, 30 Nov 2012 13:17:40 -0800
From: Greg KH <gregkh@...uxfoundation.org>
To: Dmitry Torokhov <dtor@...are.com>
Cc: pv-drivers@...are.com, Andy King <acking@...are.com>,
linux-kernel@...r.kernel.org,
virtualization@...ts.linux-foundation.org
Subject: Re: [Pv-drivers] [PATCH 12/12] VMCI: Some header and config files.
On Fri, Nov 30, 2012 at 12:58:25PM -0800, Dmitry Torokhov wrote:
> On Friday, November 30, 2012 12:44:06 PM Greg KH wrote:
> > On Fri, Nov 30, 2012 at 12:09:40PM -0800, Dmitry Torokhov wrote:
> > > On Friday, November 30, 2012 10:57:55 AM Greg KH wrote:
> > > > On Fri, Nov 30, 2012 at 10:45:44AM -0800, Dmitry Torokhov wrote:
> > > > > However you snipped the rest of my reply: do we really need to
> > > > > renumber
> > > > > ioctls? There is no benefit for the driver as its ioctl handler does
> > > > > not parse the numbers into components.
> > > >
> > > > I don't know if you need to renumber, I really don't understand what you
> > > > were trying to do with this code, and as it was acting differently from
> > > > all other kernel ioctl declarations, I asked for some clarity.
> > > >
> > > > If you can rewrite it to look sane, and keep the same numbers, that's
> > > > fine with me.
> > >
> > > OK, it looks like we can redo them as:
> > >
> > > #define IOCTL_VMCI_VERSION _IO(7, 0x9f) /* 1951 */
> > > #define IOCTL_VMCI_INIT_CONTEXT _IO(7, 0xa0) /* 1952 */
> > >
> > > Is this acceptable?
> >
> > Sure, that's better. You also got lucky, '7' happens to be unused right
> > now.
>
> Excellent. You said you want the next drop after -rc1, right?
Yes please, I will be ignoring patches until then.
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists