All of lore.kernel.org
 help / color / mirror / Atom feed
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: Wed, 19 Jun 2002 17:33:41 +0200	[thread overview]
Message-ID: <3D10A455.7682EF16@imc-berlin.de> (raw)
In-Reply-To: 20020619152528.GB12762@opus.bloom.county


Tom Rini wrote:
>
> On Wed, Jun 19, 2002 at 05:18:04PM +0200, Steven Scholz wrote:
> >
> > Tom Rini wrote:
> >
> > > I'm sort-of supprised it works.
> > I told you, it's not that much to do...
> > :-)
> >
> > > Isn't:
> > > ((uint)0x....)
> > > in assembly bad?
> >
> > Hmm. Don't know. Maybe. But these are just DEFINES! So what should that
> > be bad?
>
> Oh yeah, right..  Hmm, it probably won't break anything then..
>
> > > I think we need to have all of these defines enclosed with the
> > > __ASSEMBLY__ test, but I can go fix that.
> >
> > At least spd8xx.h and tqm8xx.h don't have any #ifndef __ASSEMBLY__ at
> > all!?
>
> (... waking up ...) Because the only C bits they had are now in
> <asm/ppcboot.h> which does the test right.
>

All right then. I can't do more testing due to the lack of hardware.
Maybe Wolfgang could spend a little of his precious time since he claims
to have a zoo of boards... :o)
(Especially TQM8xxL, FPS850L, SM850)

So when can I "bk pull" these changes then, Tom?

Good luck,

Steven

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

  reply	other threads:[~2002-06-19 15:33 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 [this message]
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=3D10A455.7682EF16@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.