public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: tglx@linutronix.de (Thomas Gleixner)
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>,
	"Steven Scholz" <steven.scholz@imc-berlin.de>
Cc: "'linux-mtd@lists.infradead.org'" <linux-mtd@lists.infradead.org>
Subject: Re: kernel oops in cfi_cmdset_0002.c:do_write_one()...
Date: Thu, 8 Apr 2004 21:28:23 +0200	[thread overview]
Message-ID: <200404082128.23060.tglx@linutronix.de> (raw)
In-Reply-To: <20040408143717.GA1921@wohnheim.fh-wedel.de>

On Thursday 08 April 2004 16:37, Jörn Engel wrote:
> On Thu, 8 April 2004 15:29:09 +0200, Steven Scholz wrote:
> > I just notice that in my old 2.4.20 kernel tree I have a
> >
> > 	* $Id: cfi_cmdset_0002.c,v 1.67 2003/04/15 22:32:13 thayne Exp $
> >
> > and in a _new_ 2.4.25 tree I have
> >
> > 	 * $Id: cfi_cmdset_0002.c,v 1.62 2003/01/24 23:30:13 dwmw2 Exp $
> >
> > How could that be !?!?
> >
> > Is the MTD code not pushed up into the main kernel sources???
>
> It is, whenever David finds the time for it.
>
> Don't blame him, this is the result of using CVS, which is designed
> around the assumption of a single central repository.  If current sync
> speed is to slow for you, try to make it easier for him to send
> patches forward.

I don't know, if he is really happy, if everybody starts to send patches 
upstream. He does a good job on this and he focussed more on 2.6 in the last 
months. But I'm sure that he can be convinced to bring 2.4 to the same state 
as 2.6 at least. On the other hand we live very well with the MTD patches 
since long, so what :) I never trust the kernel stuff of subsystems, which 
have a active development team :)

-- 
Thomas
________________________________________________________________________
"Free software" is a matter of liberty, not price. To understand the concept,
you should think of "free" as in "free speech,'' not as in "free beer".
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de

  reply	other threads:[~2004-04-08 19:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-07 15:43 kernel oops in cfi_cmdset_0002.c:do_write_one() Steven Scholz
2004-04-07 16:19 ` Thayne Harbaugh
2004-04-07 16:47   ` David Vrabel
2004-04-11 11:40     ` Steven Scholz
2004-04-08  7:16   ` Steven Scholz
2004-04-08 13:29   ` Steven Scholz
2004-04-08 14:37     ` Jörn Engel
2004-04-08 19:28       ` Thomas Gleixner [this message]
2004-04-08 19:47         ` Jörn Engel
2004-04-09 12:42       ` David Woodhouse
2004-04-13  9:31         ` Jörn Engel
2004-04-13 14:28           ` David Woodhouse
2004-04-13 11:04         ` David Vrabel
     [not found] <D73A25AA6E54D511AD74009027B1110F5BB16A@ORION>
2004-04-07 16:12 ` Steven Scholz

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=200404082128.23060.tglx@linutronix.de \
    --to=tglx@linutronix.de \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=steven.scholz@imc-berlin.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