linux-kernel - Re: [PATCH] mtd: unify mtd partition/device registration

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20081113.232823.125897716.anemo@mba.ocn.ne.jp>
Date:	Thu, 13 Nov 2008 23:28:23 +0900 (JST)
From:	Atsushi Nemoto <anemo@....ocn.ne.jp>
To:	vapier@...too.org
Cc:	linux-mtd@...ts.infradead.org, dwmw2@...radead.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mtd: unify mtd partition/device registration

On Thu, 13 Nov 2008 22:43:50 +0900 (JST), Atsushi Nemoto <anemo@....ocn.ne.jp> wrote:
> On Wed, 12 Nov 2008 18:38:53 -0500, Mike Frysinger <vapier@...too.org> 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@...too.org>
> > ---
> >  drivers/mtd/mtdcore.c   |   37 +++++++++++++++++++++++++++++++++++++
> >  include/linux/mtd/mtd.h |    3 +++
> >  2 files changed, 40 insertions(+), 0 deletions(-)
> 
> I like this idea.

Some drivers call both add_mtd_device() and add_mtd_partitions().  The
mtd_device is used to access whole flash area (like /dev/hda).  How do
you think of these usage patterns?

maps/edb7312.c
maps/mbx860.c
maps/plat-ram.c
nand/cafe_nand.c
nand/diskonchip.c
nand/ndfc.c

Automatic fallback to mtd_device in parse_mtd() is convenient but
somewhat unflexible...

---
Atsushi Nemoto
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/