[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100514092902.ba0f075a.randy.dunlap@oracle.com>
Date: Fri, 14 May 2010 09:29:02 -0700
From: Randy Dunlap <randy.dunlap@...cle.com>
To: Soren Hansen <soren@...ux2go.dk>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] Make the Xen block device prefix configurable
On Fri, 14 May 2010 18:10:48 +0200 Soren Hansen wrote:
> Add a config option to tweak the Xen block device prefix.
>
> Signed-off-by: Soren Hansen <soren@...ux2go.dk>
> Tested-By: Major Hayden <major.hayden@...kspace.com>
> ---
> drivers/block/Kconfig | 10 ++++++++++
> drivers/block/xen-blkfront.c | 2 +-
> 2 files changed, 11 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/block/Kconfig b/drivers/block/Kconfig
> index 1d886e0..89c1887 100644
> --- a/drivers/block/Kconfig
> +++ b/drivers/block/Kconfig
> @@ -467,6 +467,16 @@ config XEN_BLKDEV_FRONTEND
> block device driver. It communicates with a back-end driver
> in another domain which drives the actual block device.
>
> +config XEN_BLKDEV_NAME
> + string "Base name for Xen block devices"
> + depends on XEN_BLKDEV_FRONTEND
> + default "xvd"
> + help
> + Use this as the base name for Xen block devices. This is
> + traditionally "xvd", but if you're trying to boot a system
> + that expects to find its root device on /dev/sda, you can
> + use this setting to accomodate that.
accommodate
> +
> config VIRTIO_BLK
> tristate "Virtio block driver (EXPERIMENTAL)"
> depends on EXPERIMENTAL && VIRTIO
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
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