mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Atsushi Nemoto" <anemo@mba.ocn.ne.jp>
Cc: vapier@gentoo.org, linux-mtd@lists.infradead.org,
	dwmw2@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mtd: unify mtd partition/device registration
Date: Fri, 14 Nov 2008 13:15:40 -0500	[thread overview]
Message-ID: <8bd0f97a0811141015j1bd862a3n268e522e4369a39c@mail.gmail.com> (raw)
In-Reply-To: <20081114.232742.128619046.anemo@mba.ocn.ne.jp>

On Fri, Nov 14, 2008 at 09:27, Atsushi Nemoto wrote:
> On Fri, 14 Nov 2008 07:22:31 -0500, Mike Frysinger wrote:
>> Rather than having every map/mtd driver doing the same sequence of
>> registering partitions and/or devices, implement common parse_mtd().
>>
>> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
>> ---
>> v2:
>>       - ifdef parsers in parse_mtd()
>>       - add "always_whole" to parse_mtd()
>>       - add unparse_mtd()
>>
>>  drivers/mtd/mtdcore.c   |   60 +++++++++++++++++++++++++++++++++++++++++++++++
>>  include/linux/mtd/mtd.h |    5 ++++
>>  2 files changed, 65 insertions(+), 0 deletions(-)
>
> Though not tested yet on real hardware, all patches looks OK for me.

ive tested the various code paths with physmap on my BF548-EZKIT ...
seemed to work OK ...
-mike

      reply	other threads:[~2008-11-14 18:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-14 12:22 Mike Frysinger
2008-11-14 12:22 ` [PATCH v2] mtd/physmap: use parse_mtd() Mike Frysinger
2008-11-14 12:22 ` [PATCH v2] mtd/bfin-async-flash: " Mike Frysinger
2008-11-14 14:27 ` [PATCH v2] mtd: unify mtd partition/device registration Atsushi Nemoto
2008-11-14 18:15   ` Mike Frysinger [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=8bd0f97a0811141015j1bd862a3n268e522e4369a39c@mail.gmail.com \
    --to=vapier.adi@gmail.com \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=vapier@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®