All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: alan@lxorguk.ukuu.org.uk, arnd@arndb.de,
	kumar.gala@freescale.com, benh@kernel.crashing.org,
	greg@kroah.com, akpm@kernel.org, cmetcalf@tilera.com,
	konrad.wilk@oracle.com, dsaxena@linaro.org,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	linux-console@vger.kernel.org
Subject: Re: [PATCH 7/7] [v4] drivers/virt: introduce Freescale hypervisor management driver
Date: Wed, 8 Jun 2011 18:16:11 -0500	[thread overview]
Message-ID: <4DF002BB.1020705@freescale.com> (raw)
In-Reply-To: <20110608161009.7b05d305.randy.dunlap@oracle.com>

Randy Dunlap wrote:
>> Add the drivers/virt directory, which houses drivers that support
>> > virtualization environments, and add the Freescale hypervisor management
>> > driver.

> It can't go in linux/virt or linux/virt/fsl instead?  why drivers/ ?
> 
> or maybe linux/virt should be drivers/virt ?

I knew this would happen.  The reason I put it in drivers/virt is because Arnd
told me to put it there.  At this point, I don't give a damn where it goes, but
I wish you all would come to a consensus.

>> > + * ALTERNATIVELY, this software may be distributed under the terms of the
>> > + * GNU General Public License ("GPL") as published by the Free Software
>> > + * Foundation, either version 2 of that License or (at your option) any
>> > + * later version.

> Why any later version?  I thought that <powers> decided that Linux
> is GPL v2.

Um, you do realize that this isn't the only file in the kernel that is
v2-or-later?  Try this command on the Linux source, and you'll see what I mean:

grep -r "\(at your option\)" *

I'm dual-licensing the header file because it's meant for applications as well
as the kernel.  That way, no one needs to worry whether #including the header
file in his application will taint the app with the GPL.

>> > +/**
>> > + * struct fsl_hv_ioctl_restart: restart a partition
> This syntax should be (for all structs here):
> 
>  * struct fsl_hv_ioctl_restart - restart a partition
> 
> but the struct fields/members do use ':' instead of '-'.
> 
> Darn, I checked Documentation/kernel-doc-nano-HOWTO.txt and it says
> that ':' is optional but '-' is needed, so you could use
> 
>  * struct fsl_hv_ioctl_restart: - restart a partition
> 

Ok, I'll change it.

>> > + * fsl_hv_event_register -- register a callback for failover events

> Documentation/kernel-doc-nano-HOWTO.txt says to use one '-' here, not 2.

Ok.  I'll review that document and make sure my comments conform.  I guess I
just wasn't paying attention at the time.

-- 
Timur Tabi
Linux kernel developer at Freescale


WARNING: multiple messages have this Message-ID (diff)
From: Timur Tabi <timur@freescale.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: arnd@arndb.de, konrad.wilk@oracle.com, kumar.gala@freescale.com,
	linux-kernel@vger.kernel.org, cmetcalf@tilera.com,
	akpm@kernel.org, dsaxena@linaro.org,
	linux-console@vger.kernel.org, greg@kroah.com,
	linuxppc-dev@lists.ozlabs.org, alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH 7/7] [v4] drivers/virt: introduce Freescale hypervisor management driver
Date: Wed, 8 Jun 2011 18:16:11 -0500	[thread overview]
Message-ID: <4DF002BB.1020705@freescale.com> (raw)
In-Reply-To: <20110608161009.7b05d305.randy.dunlap@oracle.com>

Randy Dunlap wrote:
>> Add the drivers/virt directory, which houses drivers that support
>> > virtualization environments, and add the Freescale hypervisor management
>> > driver.

> It can't go in linux/virt or linux/virt/fsl instead?  why drivers/ ?
> 
> or maybe linux/virt should be drivers/virt ?

I knew this would happen.  The reason I put it in drivers/virt is because Arnd
told me to put it there.  At this point, I don't give a damn where it goes, but
I wish you all would come to a consensus.

>> > + * ALTERNATIVELY, this software may be distributed under the terms of the
>> > + * GNU General Public License ("GPL") as published by the Free Software
>> > + * Foundation, either version 2 of that License or (at your option) any
>> > + * later version.

> Why any later version?  I thought that <powers> decided that Linux
> is GPL v2.

Um, you do realize that this isn't the only file in the kernel that is
v2-or-later?  Try this command on the Linux source, and you'll see what I mean:

grep -r "\(at your option\)" *

I'm dual-licensing the header file because it's meant for applications as well
as the kernel.  That way, no one needs to worry whether #including the header
file in his application will taint the app with the GPL.

>> > +/**
>> > + * struct fsl_hv_ioctl_restart: restart a partition
> This syntax should be (for all structs here):
> 
>  * struct fsl_hv_ioctl_restart - restart a partition
> 
> but the struct fields/members do use ':' instead of '-'.
> 
> Darn, I checked Documentation/kernel-doc-nano-HOWTO.txt and it says
> that ':' is optional but '-' is needed, so you could use
> 
>  * struct fsl_hv_ioctl_restart: - restart a partition
> 

Ok, I'll change it.

>> > + * fsl_hv_event_register -- register a callback for failover events

> Documentation/kernel-doc-nano-HOWTO.txt says to use one '-' here, not 2.

Ok.  I'll review that document and make sure my comments conform.  I guess I
just wasn't paying attention at the time.

-- 
Timur Tabi
Linux kernel developer at Freescale

WARNING: multiple messages have this Message-ID (diff)
From: Timur Tabi <timur@freescale.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: <alan@lxorguk.ukuu.org.uk>, <arnd@arndb.de>,
	<kumar.gala@freescale.com>, <benh@kernel.crashing.org>,
	<greg@kroah.com>, <akpm@kernel.org>, <cmetcalf@tilera.com>,
	<konrad.wilk@oracle.com>, <dsaxena@linaro.org>,
	<linuxppc-dev@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>,
	<linux-console@vger.kernel.org>
Subject: Re: [PATCH 7/7] [v4] drivers/virt: introduce Freescale hypervisor management driver
Date: Wed, 8 Jun 2011 18:16:11 -0500	[thread overview]
Message-ID: <4DF002BB.1020705@freescale.com> (raw)
In-Reply-To: <20110608161009.7b05d305.randy.dunlap@oracle.com>

Randy Dunlap wrote:
>> Add the drivers/virt directory, which houses drivers that support
>> > virtualization environments, and add the Freescale hypervisor management
>> > driver.

> It can't go in linux/virt or linux/virt/fsl instead?  why drivers/ ?
> 
> or maybe linux/virt should be drivers/virt ?

I knew this would happen.  The reason I put it in drivers/virt is because Arnd
told me to put it there.  At this point, I don't give a damn where it goes, but
I wish you all would come to a consensus.

>> > + * ALTERNATIVELY, this software may be distributed under the terms of the
>> > + * GNU General Public License ("GPL") as published by the Free Software
>> > + * Foundation, either version 2 of that License or (at your option) any
>> > + * later version.

> Why any later version?  I thought that <powers> decided that Linux
> is GPL v2.

Um, you do realize that this isn't the only file in the kernel that is
v2-or-later?  Try this command on the Linux source, and you'll see what I mean:

grep -r "\(at your option\)" *

I'm dual-licensing the header file because it's meant for applications as well
as the kernel.  That way, no one needs to worry whether #including the header
file in his application will taint the app with the GPL.

>> > +/**
>> > + * struct fsl_hv_ioctl_restart: restart a partition
> This syntax should be (for all structs here):
> 
>  * struct fsl_hv_ioctl_restart - restart a partition
> 
> but the struct fields/members do use ':' instead of '-'.
> 
> Darn, I checked Documentation/kernel-doc-nano-HOWTO.txt and it says
> that ':' is optional but '-' is needed, so you could use
> 
>  * struct fsl_hv_ioctl_restart: - restart a partition
> 

Ok, I'll change it.

>> > + * fsl_hv_event_register -- register a callback for failover events

> Documentation/kernel-doc-nano-HOWTO.txt says to use one '-' here, not 2.

Ok.  I'll review that document and make sure my comments conform.  I guess I
just wasn't paying attention at the time.

-- 
Timur Tabi
Linux kernel developer at Freescale


  reply	other threads:[~2011-06-08 23:16 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-08 22:45 [PATCH 7/7] [v4] drivers/virt: introduce Freescale hypervisor management driver Timur Tabi
2011-06-08 22:45 ` Timur Tabi
2011-06-08 23:10 ` Randy Dunlap
2011-06-08 23:10   ` Randy Dunlap
2011-06-08 23:10   ` Randy Dunlap
2011-06-08 23:16   ` Timur Tabi [this message]
2011-06-08 23:16     ` Timur Tabi
2011-06-08 23:16     ` Timur Tabi
2011-06-09  7:38   ` Arnd Bergmann
2011-06-09  7:38   ` Arnd Bergmann
2011-06-09  7:38     ` Arnd Bergmann
2011-06-09 16:32     ` Randy Dunlap
2011-06-09 16:32       ` Randy Dunlap
2011-06-09 16:36       ` Timur Tabi
2011-06-09 16:36         ` Timur Tabi
2011-06-09 16:36         ` Timur Tabi
2011-06-09 16:42         ` Randy Dunlap
2011-06-09 16:42         ` Randy Dunlap
2011-06-09 16:42           ` Randy Dunlap
2011-06-09 16:48           ` Timur Tabi
2011-06-09 16:48           ` Timur Tabi
2011-06-09 16:48             ` Timur Tabi
2011-06-09 16:48             ` Timur Tabi
2011-06-09 16:36       ` Timur Tabi
2011-06-09 16:32     ` Randy Dunlap
2011-06-10 14:17     ` Chris Metcalf
2011-06-10 14:17     ` Chris Metcalf
2011-06-10 14:17       ` Chris Metcalf
2011-06-10 14:17       ` Chris Metcalf
2011-06-10 15:36       ` Arnd Bergmann
2011-06-10 15:36       ` Arnd Bergmann
2011-06-10 15:36         ` Arnd Bergmann
2011-06-09  7:29 ` Arnd Bergmann
2011-06-09  7:29   ` Arnd Bergmann
2011-06-09 18:55   ` Timur Tabi
2011-06-09 18:55     ` Timur Tabi
2011-06-09 18:55     ` Timur Tabi
2011-06-09 20:20     ` Arnd Bergmann
2011-06-09 20:20       ` Arnd Bergmann
2011-06-09 20:24       ` Timur Tabi
2011-06-09 20:24         ` Timur Tabi
2011-06-09 20:24         ` Timur Tabi

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=4DF002BB.1020705@freescale.com \
    --to=timur@freescale.com \
    --cc=akpm@kernel.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arnd@arndb.de \
    --cc=benh@kernel.crashing.org \
    --cc=cmetcalf@tilera.com \
    --cc=dsaxena@linaro.org \
    --cc=greg@kroah.com \
    --cc=konrad.wilk@oracle.com \
    --cc=kumar.gala@freescale.com \
    --cc=linux-console@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=randy.dunlap@oracle.com \
    /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.