All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Daniel Golle <daniel@makrotopia.org>,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>,
	Richard Weinberger <richard@nod.at>,
	Matthew Wilcox <willy@infradead.org>,
	Jens Axboe <axboe@kernel.dk>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Chaitanya Kulkarni <kch@nvidia.com>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: Re: [RFC PATCH 2/2] block: add uImage.FIT block partition driver
Date: Tue, 13 Dec 2022 08:45:44 -0800	[thread overview]
Message-ID: <aae11fd8-03c0-7996-67ca-7b528a6fec15@infradead.org> (raw)
In-Reply-To: <Y5h0C4iKoeCJgRCb@makrotopia.org>



On 12/13/22 04:46, Daniel Golle wrote:
> diff --git a/drivers/block/Kconfig b/drivers/block/Kconfig
> index a41145d52de9..f8618bc869b2 100644
> --- a/drivers/block/Kconfig
> +++ b/drivers/block/Kconfig
> @@ -383,6 +383,17 @@ config VIRTIO_BLK
>  	  This is the virtual block driver for virtio.  It can be used with
>            QEMU based VMMs (like KVM or Xen).  Say Y or M.
>  
> +config UIMAGE_FIT_BLK
> +	bool "uImage.FIT block driver"
> +	help
> +	  This is driver allows using filesystems contained in uImage.FIT images

	  This driver allows

> +	  by mapping them as block devices.
> +
> +	  This driver can currently not be built as a module.
> +
> +	  Say Y if you want to mount filesystems sub-images of a uImage.FIT
> +	  stored in a block device partition, mtdblock or ubiblock device.

-- 
~Randy

  reply	other threads:[~2022-12-13 16:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13 12:46 [RFC PATCH 2/2] block: add uImage.FIT block partition driver Daniel Golle
2022-12-13 16:45 ` Randy Dunlap [this message]
2022-12-15  8:11 ` Christoph Hellwig

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=aae11fd8-03c0-7996-67ca-7b528a6fec15@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=daniel@makrotopia.org \
    --cc=hch@infradead.org \
    --cc=kch@nvidia.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=richard@nod.at \
    --cc=willy@infradead.org \
    --cc=wsa+renesas@sang-engineering.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.