From: Steven Scholz <steven.scholz@imc-berlin.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: board specific defines in commproc.h !?!?
Date: Mon, 17 Jun 2002 18:01:30 +0200 [thread overview]
Message-ID: <3D0E07DA.327DF963@imc-berlin.de> (raw)
In-Reply-To: 20020617154925.GT13541@opus.bloom.county
Tom Rini wrote:
> > Ehm... Does that mean you won't accept patches vs linuxppc-2.4 though
> > !?!?
>
> That means I want this to be done in 2.5 first. Where development is
> supposed to happen. I have this feeling that fixing commproc.h will be
> more than 1 simple patch and we should do it in the development tree
> first. Then, once that's all done and people are happy with it, we can
> move it to linuxppc_2_4.
Hmm... Just moving the DEFINEs from commproc.h to the board specific
header files is indeed just ONE simple patch. I've done that already. I
am not sure what else you mean by "fixing commproc.h"!?
The thing is:
Since I am sure that many, many people are still using linux-2.4.4 I
would realy like to fix that in linuxppc_2_4_devel, linux-2.4.4 (DENX)
_and_ PPCBoot at the same time! Just to keep that consistent.
And I have to admit that I haven't had a look at linuxppc-2.5 at all so
far... :-(
Steven
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-06-17 16:01 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 [this message]
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
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=3D0E07DA.327DF963@imc-berlin.de \
--to=steven.scholz@imc-berlin.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.