From: Lennert Buytenhek <buytenh@wantstofly.org>
To: Jared Hulbert <jaredeh@gmail.com>
Cc: linux-mtd@lists.infradead.org, nico@cam.org,
David Woodhouse <dwmw2@infradead.org>,
Alexey Korolev <akorolev@infradead.org>
Subject: Re: [RFC/PATCH 8/8] LPDDR extended physmap driver to support LPDDR flash.
Date: Fri, 17 Oct 2008 03:06:43 +0200 [thread overview]
Message-ID: <20081017010643.GE14569@xi.wantstofly.org> (raw)
In-Reply-To: <6934efce0810161730l2aa66f30v83c6ed644e0d6707@mail.gmail.com>
On Thu, Oct 16, 2008 at 05:30:27PM -0700, Jared Hulbert wrote:
> > I'd rather not extend the MTD_PHYSMAP_xxx options; in fact I'd prefer to
> > phase them out completely. The platform device and the device tree
> > should be perfectly sufficient.
>
> Can you explain your plan here? I like physmap. The more powerful it
> is the fewer devices need to be described.
IMHO it's fine if physmap gets additional options, but those extra
options should be configured via platform data, and not via the legacy
CONFIG_MTD_PHYSMAP_xxx kernel config options.
next prev parent reply other threads:[~2008-10-17 1:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 21:39 [RFC/PATCH 8/8] LPDDR extended physmap driver to support LPDDR flash Alexey Korolev
2008-10-14 10:20 ` David Woodhouse
2008-10-14 13:10 ` Alexey Korolev
2008-10-17 0:30 ` Jared Hulbert
2008-10-17 1:06 ` Lennert Buytenhek [this message]
2008-10-17 17:27 ` Jared Hulbert
2008-10-17 17:43 ` Alexey Korolev
2008-10-17 17:58 ` Jared Hulbert
2008-10-17 17:59 ` David Woodhouse
2008-10-17 18:03 ` Jared Hulbert
2008-10-17 18:06 ` Lennert Buytenhek
2008-10-17 18:12 ` Nicolas Pitre
2008-10-18 2:54 ` Jared Hulbert
2008-10-18 15:46 ` Lennert Buytenhek
2008-10-18 18:20 ` Jared Hulbert
2008-10-18 19:59 ` Nicolas Pitre
2008-10-19 0:47 ` Jared Hulbert
2008-10-19 1:38 ` Nicolas Pitre
2008-10-17 18:01 ` Lennert Buytenhek
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=20081017010643.GE14569@xi.wantstofly.org \
--to=buytenh@wantstofly.org \
--cc=akorolev@infradead.org \
--cc=dwmw2@infradead.org \
--cc=jaredeh@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=nico@cam.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