All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Shmulik Ladkani <shmulik.ladkani@gmail.com>
Cc: Huang Shijie <b32955@freescale.com>,
	linux-mtd@lists.infradead.org, Huang Shijie <shijie8@gmail.com>
Subject: Re: [PATCH 1/3] mtd: cmdlinepart: make the partitions rule more strict
Date: Sat, 22 Sep 2012 19:01:29 +0300	[thread overview]
Message-ID: <1348329689.1894.4.camel@kyv> (raw)
In-Reply-To: <20120905083020.0bf6b0bd@halley>

[-- Attachment #1: Type: text/plain, Size: 841 bytes --]

On Wed, 2012-09-05 at 08:30 +0300, Shmulik Ladkani wrote:
> On Wed, 5 Sep 2012 10:12:20 +0800 Huang Shijie <b32955@freescale.com> wrote:
> > yes, it's really simple and flexible.
> > But I think it's not wise to export the 0-size partition to user.
> > The user may confused at this.
> > 
> > And the mtd-utils, such as mtd-info/mtd-debug, do they can work with a 
> > 0-size partition?
> 
> I think the 0 sized partition case is really seldom, don't worth the
> trouble, the user will probably observe something went wrong in his
> cmdline parts specification.
> 
> But nevertheless, if we think it's a MUST to forbid the 0 sized
> partitions, then amend my patch as follows:

OK, pushed this one to l2-mtd.git. Guys, if there are more patches on
top of this, please, re-send them.

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-09-22 16:01 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-26 17:21 [PATCH 1/3] mtd: cmdlinepart: make the partitions rule more strict Huang Shijie
2012-08-26 17:21 ` Huang Shijie
2012-08-26 17:21 ` [PATCH 2/3] mtd: cmdlinepart: sort the unsorted partitions Huang Shijie
2012-08-26 17:21   ` Huang Shijie
2012-08-31 13:59   ` Artem Bityutskiy
2012-08-31 13:59     ` Artem Bityutskiy
2012-08-31 14:29     ` Huang Shijie
2012-08-31 14:29       ` Huang Shijie
2012-09-03  7:21   ` Artem Bityutskiy
2012-09-03  7:21     ` Artem Bityutskiy
2012-08-26 17:21 ` [PATCH 3/3] mtd: cmdlinepart: fix the wrong partitions number when truncating occurs Huang Shijie
2012-08-26 17:21   ` Huang Shijie
2012-08-30  6:43   ` Artem Bityutskiy
2012-08-30  6:43     ` Artem Bityutskiy
2012-08-30  6:39     ` Huang Shijie
2012-08-30  6:39       ` Huang Shijie
2012-08-31 11:45 ` [PATCH 1/3] mtd: cmdlinepart: make the partitions rule more strict Artem Bityutskiy
2012-08-31 11:45   ` Artem Bityutskiy
2012-08-31 13:36   ` Huang Shijie
2012-08-31 13:36     ` Huang Shijie
2012-08-31 14:30   ` Huang Shijie
2012-08-31 14:30     ` Huang Shijie
2012-09-03  7:18 ` Artem Bityutskiy
2012-09-03  7:18   ` Artem Bityutskiy
2012-09-03 15:09   ` Huang Shijie
2012-09-03 15:09     ` Huang Shijie
2012-09-03 15:35     ` Artem Bityutskiy
2012-09-04  3:23       ` Huang Shijie
2012-09-04 11:48       ` Shmulik Ladkani
2012-09-05  2:12         ` Huang Shijie
2012-09-05  5:30           ` Shmulik Ladkani
2012-09-22 16:01             ` Artem Bityutskiy [this message]
2012-12-17  1:11           ` Christopher Cordahi
2012-12-18  5:27             ` Brian Norris
2013-01-15 11:49             ` Artem Bityutskiy

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=1348329689.1894.4.camel@kyv \
    --to=dedekind1@gmail.com \
    --cc=b32955@freescale.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=shijie8@gmail.com \
    --cc=shmulik.ladkani@gmail.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.