linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Dan Malek <dan@embeddededge.com>
Cc: Tom Rini <trini@kernel.crashing.org>,
	Steven Scholz <steven.scholz@imc-berlin.de>,
	LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: board specific defines in commproc.h !?!?
Date: Thu, 20 Jun 2002 00:15:27 +0200	[thread overview]
Message-ID: <20020619221532.F3C7A10301@denx.denx.de> (raw)
In-Reply-To: Your message of "Wed, 19 Jun 2002 17:11:36 EDT." <3D10F388.5@embeddededge.com>


Dan,

in message <3D10F388.5@embeddededge.com> you wrote:
>
> The 2.4 source base is no longer supposed to be a development base.
...
> kernel is what it is, like it or not.  If you want something new and different,
> it belongs in the 2.5 tree to show up at some point in the future.

So what is your suggestion if I want to provide a patch that supports
some new hardware?

Obviously I want to get it added to a stable tree, so we can  use  it
in  a real project. And often enough the hardware is instable enough,
so I don't need the additional thrill of an instable Linux kernel.


I understand that 2.4 should get stable, but  there  is  a  huge  gap
between  2.4  and 2.5, so neither fits - well, actually 2.4 fits _my_
requirements.

What do you recommend to do?

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
All these theories, diverse as they are, have two things  in  common:
they explain the observed facts, and they are completeley and utterly
wrong.                       - Terry Pratchett, _The Light Fantastic_

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

  parent reply	other threads:[~2002-06-19 22:15 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-17  9:20 board specific defines in commproc.h !?!? Steven Scholz
2002-06-17 14:05 ` John W. Linville
2002-06-17 15:32 ` Tom Rini
2002-06-17 15:37   ` Steven Scholz
2002-06-17 15:49     ` Tom Rini
2002-06-17 16:01       ` Steven Scholz
2002-06-17 16:28         ` Tom Rini
2002-06-17 17:25   ` Wolfgang Denk
     [not found]     ` <20020617173550.GV13541@opus.bloom.county>
2002-06-17 17:46       ` Steven Scholz
2002-06-17 20:23       ` Wolfgang Denk
     [not found] ` <3D106922.7026437A@imc-berlin.de>
2002-06-19 15:05   ` Tom Rini
2002-06-19 15:18     ` Steven Scholz
2002-06-19 15:25       ` Tom Rini
2002-06-19 15:33         ` Steven Scholz
2002-06-19 15:41           ` Tom Rini
2002-06-19 15:47             ` Steven Scholz
2002-06-19 15:51               ` Tom Rini
2002-06-19 21:11         ` Dan Malek
2002-06-19 21:22           ` Tom Rini
2002-06-20 16:32             ` Dan Malek
2002-06-19 22:15           ` Wolfgang Denk [this message]
2002-06-19 23:26             ` Conn Clark
2002-06-20 16:40             ` Dan Malek
     [not found]               ` <3D12F140.23BA447F@imc-berlin.de>
     [not found]                 ` <15635.12386.415897.593660@argo.ozlabs.ibm.com>
2002-06-21 14:18                   ` John Traill
     [not found] <20020617214339.GZ13541@opus.bloom.county>
2002-06-17 22:28 ` Wolfgang Denk

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=20020619221532.F3C7A10301@denx.denx.de \
    --to=wd@denx.de \
    --cc=dan@embeddededge.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=steven.scholz@imc-berlin.de \
    --cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).