All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Jamie Iles <jamie@jamieiles.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Removing CONFIG_MTD_PARTITIONS
Date: Thu, 12 May 2011 14:55:27 +0300	[thread overview]
Message-ID: <1305201327.2713.101.camel@localhost> (raw)
In-Reply-To: <20110509095604.GA10860@pulham.picochip.com>

On Mon, 2011-05-09 at 10:56 +0100, Jamie Iles wrote:
> I've had a quick look at removing CONFIG_MTD_PARTITIONS so that MTD 
> partitioning is always enabled and the patch below is what I have so 
> far.

Thanks!

> At the moment this just always builds in partitioning support and 
> introduces mtd_device_{,un}register() (I'm not sure if these are the 
> best names).  These effectively replace 
> add_mtd_device()/add_mtd_partitions() and their deletion counterparts 
> and will register partitions if supplied, or the whole device if there 
> are no partitions.  I've also converted over a couple of mtd drivers, 
> and will do them all if this is the correct approach.
> 
> I've left CONFIG_MTD_PARTITIONS as a bool with no description to keep 
> the series bisectable - the final patch would remove it completely and 
> make add_mtd_device and add_mtd_partitions internal only symbols.  Does 
> this seem like a reasonable strategy?

Looks like. Could you please split this patch on a series of small and
easily reviewable patches?

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

      reply	other threads:[~2011-05-12 11:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-09  9:56 Removing CONFIG_MTD_PARTITIONS Jamie Iles
2011-05-12 11:55 ` Artem Bityutskiy [this message]

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=1305201327.2713.101.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=jamie@jamieiles.com \
    --cc=linux-mtd@lists.infradead.org \
    /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.