public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@sirena.org.uk>
To: J?rn Engel <joern@wohnheim.fh-wedel.de>
Cc: linux-mtd@lists.infradead.org,
	Lennert Buytenhek <buytenh@wantstofly.org>
Subject: Re: [less intrusive PATCH, RFC] don't load physmap if length is zero
Date: Mon, 13 Mar 2006 18:47:30 +0000	[thread overview]
Message-ID: <20060313184729.GB19014@sirena.org.uk> (raw)
In-Reply-To: <20060312221248.GA7525@wohnheim.fh-wedel.de>

On Sun, Mar 12, 2006 at 11:12:48PM +0100, J?rn Engel wrote:
> On Tue, 28 February 2006 20:16:42 +0100, Lennert Buytenhek wrote:

> > I'd still prefer the platform driver patch to be applied, but having
> > some kind of solution merged is better than no solution at all :-)

> Is there a good reason why you didn't just write your own mapping
> driver?  Most people copy physmap.c, change a few things and use that
> driver instead of physmap.c.  It does involve many copies of
> essentially the same code, but that code is very simple and no sane
> kernel should have more than one mapping driver included, so no object
> code is duplicated.

It is reasonable to have multiple board variants with differing flash
setups but still want them all to run the same kernel.  If you're using
platform devices to tell the world about the rest of the differing fit
information it's reasonable to also want to use it for the flash.

-- 
"You grabbed my hand and we fell into it, like a daydream - or a fever."

  reply	other threads:[~2006-03-13 18:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-12 17:04 [PATCH,RFC] convert physmap to platform driver Lennert Buytenhek
2006-02-21 13:51 ` Lennert Buytenhek
2006-03-03  9:09   ` Deepak Saxena
2006-02-28 19:16 ` [less intrusive PATCH,RFC] don't load physmap if length is zero Lennert Buytenhek
2006-03-12 22:12   ` [less intrusive PATCH, RFC] " Jörn Engel
2006-03-13 18:47     ` Mark Brown [this message]
2006-03-13 19:14       ` Jörn Engel
2006-03-14 20:03         ` Mark Brown

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=20060313184729.GB19014@sirena.org.uk \
    --to=broonie@sirena.org.uk \
    --cc=buytenh@wantstofly.org \
    --cc=joern@wohnheim.fh-wedel.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox