[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Wed, 7 Jul 2010 04:08:54 -0700 (PDT)
From: David Brownell <david-b@...bell.net>
To: 'David Woodhouse' <dwmw2@...radead.org>,
'Kevin Hilman' <khilman@...prootsystems.com>,
Sudhakar Rajashekhara <sudhakar.raj@...com>
Cc: 'Bernd Schmidt' <bernd.schmidt@...log.com>,
'Nicolas Pitre' <nico@...xnic.net>,
linux-kernel@...r.kernel.org,
'David Howells' <dhowells@...hat.com>,
'David Brownell' <dbrownell@...rs.sourceforge.net>,
linux-mtd@...ts.infradead.org,
'Andrew Morton' <akpm@...ux-foundation.org>
Subject: RE: [PATCH 1/2] mtdpart: memory accessor interface for MTD layer
> > > This patch adds two new members to the
> mtd_partition structure,
> > > a function handler which will be
> > > called during setup of the
> > > partition and an argument to be passed to this
> setup function.
> >
> > Ick.
> >
> > I don't mind providing the mtd_macc_{read,write}
> helper functions,
> > although they should work on generic MTD
> > >devices not just on partitions.
> > But do we really have to do the callout to
> > arbitrary functions from
> > _within_ the core MTD code... why can't we
> > do that in the board driver?
I think the short answer is that the callout is
what provides the board drivers enough information
to make the correct calls.
--
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/
Powered by blists - more mailing lists