public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: David Woodhouse <dwmw2@infradead.org>,
	linux-mtd@lists.infradead.org, Marc Singer <elf@buici.com>
Subject: Re: [PATCH] MTD Maps driver for Sharp LH7a40x
Date: Sat, 19 Jun 2004 12:01:46 +0100	[thread overview]
Message-ID: <20040619120146.A28048@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200406191151.53437.tglx@linutronix.de>; from tglx@linutronix.de on Sat, Jun 19, 2004 at 11:51:53AM +0200

On Sat, Jun 19, 2004 at 11:51:53AM +0200, Thomas Gleixner wrote:
> So a final conclusion would be:
> 
> 1. Add commandline parsing for flashbase,size,buswidth which covers the case 
> where no special code is neccecary to access the chips.

I don't have strong views on this, but if the platform model is going
to be used (so that we get the VPP and WP enable code), there seems to
be little point in separating this out into the boot loader.

Other than that, it seems fine.

  reply	other threads:[~2004-06-19 11:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-13 21:43 [PATCH] MTD Maps driver for Sharp LH7a40x Marc Singer
2004-06-14  0:07 ` Thomas Gleixner
2004-06-14  0:54   ` Marc Singer
2004-06-19  0:05     ` Jun Sun
2004-06-19  0:16       ` Thomas Gleixner
2004-06-19  0:38         ` Marc Singer
2004-06-19  8:19           ` Thomas Gleixner
2004-06-19  9:23             ` Russell King - ARM Linux
2004-06-19  9:51               ` Thomas Gleixner
2004-06-19 11:01                 ` Russell King - ARM Linux [this message]
     [not found] <083AB380E3924D4795740AAE9A27DCAB7B89B3@cgy2000.interalia.ca>
2004-06-19 17:03 ` David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2004-06-12 16:47 Marc Singer
2004-06-13 19:34 ` Thomas Gleixner

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=20040619120146.A28048@flint.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=dwmw2@infradead.org \
    --cc=elf@buici.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=tglx@linutronix.de \
    /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