Linux virtualization list
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Timur Tabi <timur@freescale.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	konrad.wilk@oracle.com, greg@kroah.com, kumar.gala@freescale.com,
	linux-kernel@vger.kernel.org, cmetcalf@tilera.com,
	Linux Virtualization <virtualization@lists.linux-foundation.org>,
	dsaxena@linaro.org, linux-console@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org, alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH 7/7] [v4] drivers/virt: introduce Freescale hypervisor management driver
Date: Thu, 09 Jun 2011 09:42:29 -0700	[thread overview]
Message-ID: <4DF0F7F5.5050107__13123.413854237$1307637808$gmane$org@oracle.com> (raw)
In-Reply-To: <4DF0F672.8040206@freescale.com>

On 06/09/11 09:36, Timur Tabi wrote:
> Randy Dunlap wrote:
>> But it sounds like virt/ needs virt/host/ and virt/guest/ to me.
> 
> I'm okay with that idea, except there's a consensus that drivers should be in
> drivers/.
> 

Like sound/ ?

but what makes it a "driver"?

-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  parent reply	other threads:[~2011-06-09 16:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1307573154-15838-1-git-send-email-timur@freescale.com>
     [not found] ` <20110608161009.7b05d305.randy.dunlap@oracle.com>
2011-06-09  7:38   ` [PATCH 7/7] [v4] drivers/virt: introduce Freescale hypervisor management driver Arnd Bergmann
     [not found]   ` <201106090938.23027.arnd@arndb.de>
2011-06-09 16:32     ` Randy Dunlap
     [not found]     ` <4DF0F5A1.5080008@oracle.com>
2011-06-09 16:36       ` Timur Tabi
     [not found]       ` <4DF0F672.8040206@freescale.com>
2011-06-09 16:42         ` Randy Dunlap [this message]
     [not found]         ` <4DF0F7F5.5050107@oracle.com>
2011-06-09 16:48           ` Timur Tabi
2011-06-10 14:17     ` Chris Metcalf
     [not found]     ` <4DF22770.4010103@tilera.com>
2011-06-10 15:36       ` Arnd Bergmann

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='4DF0F7F5.5050107__13123.413854237$1307637808$gmane$org@oracle.com' \
    --to=randy.dunlap@oracle.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arnd@arndb.de \
    --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=timur@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox