LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Marius Groeger <mag@sysgo.de>
Cc: David Gibson <david@gibson.dropbear.id.au>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: Arctic-2 MTD driver
Date: Mon, 16 Dec 2002 08:31:28 -0700	[thread overview]
Message-ID: <20021216153128.GL6095@opus.bloom.county> (raw)
In-Reply-To: <Pine.LNX.4.40.0212161624180.10282-100000@mag.devdep.sysgo.de>


On Mon, Dec 16, 2002 at 04:28:06PM +0100, Marius Groeger wrote:
> On Mon, 16 Dec 2002, Tom Rini wrote:
>
> > On Mon, Dec 16, 2002 at 09:46:50AM +0100, Marius Groeger wrote:
> > >
> > > Hello David,
> > >
> > > On Mon, 16 Dec 2002, David Gibson wrote:
> > >
> > > > Having committed the core support code for the Arctic-2, here come
> > > > some drivers for it.  Below is an MTD map for the Arctic-2, derived
> > > > from beech-mtd.c.  Essentially all it does is provide suitable
> > > > hardwired partitions.
> > >
> > > Can you also post this to the linux-mtd folks?
> >
> > No point in doing that yet, as the underlying support code for the
> > Arctic-2 won't be making Marcelo's tree for a while yet.
>
> I don't see a point in NOT doing this. It will have to be done anyway,
> so David might as well do it now and be done with it.

Unusable, untestable code which may or may not need minor changes before
going upstream? (For example, I need to go and do similar changes to an
upstream version of maps/Config.in like I just did to the _devel ones).

There's no real advantage to doing it now or later, in other words. :)

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-12-16 15:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-16  2:09 Arctic-2 MTD driver David Gibson
2002-12-16  8:46 ` Marius Groeger
2002-12-16 15:01   ` Tom Rini
2002-12-16 15:28     ` Marius Groeger
2002-12-16 15:31       ` Tom Rini [this message]
2002-12-16 14:43 ` Tom Rini
2002-12-17  4:16   ` David Gibson

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=20021216153128.GL6095@opus.bloom.county \
    --to=trini@kernel.crashing.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=mag@sysgo.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