From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from galois.linutronix.de ([2001:470:1f0b:1c35:abcd:42:0:1]) by merlin.infradead.org with esmtps (Exim 4.76 #1 (Red Hat Linux)) id 1S5O0a-0004oa-Gf for linux-mtd@lists.infradead.org; Wed, 07 Mar 2012 21:02:52 +0000 Message-ID: <4F57CCF4.6040902@linutronix.de> Date: Wed, 07 Mar 2012 22:02:44 +0100 From: Richard Weinberger MIME-Version: 1.0 To: dedekind1@gmail.com Subject: Re: [RFC][PATCH 1/7] MTD: UBI: Add checkpoint on-chip layout References: <1329250006-22944-1-git-send-email-rw@linutronix.de> <1329250006-22944-2-git-send-email-rw@linutronix.de> <1331136589.3463.3.camel@sauron.fi.intel.com> In-Reply-To: <1331136589.3463.3.camel@sauron.fi.intel.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: tglx@linutronix.de, linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org, tim.bird@am.sony.com List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Am 07.03.2012 17:09, schrieb Artem Bityutskiy: > On Tue, 2012-02-14 at 21:06 +0100, Richard Weinberger wrote: >> Specify the on-chip checkpoint layout. >> The checkpoint consists of two major parts. >> A super block (identified via UBI_CP_SB_VOLUME_ID) and >> zero or more data blocks (identified via UBI_CP_DATA_VOLUME_ID). >> Data blocks are only used if whole checkpoint information does not fit >> into the super block. > > And superblock is also a more or less standard name used by file-system. > I easily imagine difficulties and confusion when discussing UBIFS and > UBI and mixing UBI and UBIFS supersblocks up. IMHO, anything unique is > much better, even if it does not make much sense. E.g., "boss block" or > "pomo block" (pomo = boss in Finnish). > > Would you consider picking a different name as well please? > Will do. Thanks, //richard