From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga02.intel.com ([134.134.136.20]) by merlin.infradead.org with esmtp (Exim 4.80.1 #2 (Red Hat Linux)) id 1WL9Wt-0004LV-Ht for linux-mtd@lists.infradead.org; Wed, 05 Mar 2014 10:58:28 +0000 Message-ID: <1394017054.6302.46.camel@sauron.fi.intel.com> Subject: Re: [PATCH v7 1/3] ubi: Introduce read-only block devices on top of UBI volumes From: Artem Bityutskiy To: Ezequiel Garcia Date: Wed, 05 Mar 2014 12:57:34 +0200 In-Reply-To: <1393245564-23947-2-git-send-email-ezequiel.garcia@free-electrons.com> References: <1393245564-23947-1-git-send-email-ezequiel.garcia@free-electrons.com> <1393245564-23947-2-git-send-email-ezequiel.garcia@free-electrons.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Cc: Thomas Petazzoni , Mike Frysinger , Richard Weinberger , Michael Opdenacker , linux-mtd@lists.infradead.org, Piergiorgio Beruto , Brian Norris , David Woodhouse , Willy Tarreau Reply-To: dedekind1@gmail.com List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, 2014-02-24 at 09:39 -0300, Ezequiel Garcia wrote: > +/* Attach a block device to an UBI volume */ > +#define UBI_IOCVOLATTBLK _IO(UBI_VOL_IOC_MAGIC, 7) Ezequiel, please, change this before it goes upstream and instead, make the ioctls accept a 'struct ubi_blkcreate_req' object pointer. /** * blah * @padding1: reserved for future, not used, has to be zeroed */ struct ubi_blkcreate_req { __s8 padding1[128]; } __packed; This will make sure we have a possibility to extend this ioctl in the future with something like volume creation flags etc. Otherwise, if we need to add a flag, we'll have to introduce a new ioctl. Thanks! -- Best Regards, Artem Bityutskiy