From: Armin <akuster@pacbell.net>
To: Stefan Roese <stefan.roese@esd-electronics.com>
Cc: David Gibson <david@gibson.dropbear.id.au>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: ppc4xx_serial.c?
Date: Thu, 14 Feb 2002 08:06:01 +0000 [thread overview]
Message-ID: <3C6B6FE9.6030406@pacbell.net> (raw)
In-Reply-To: EFEAIMDCOOOHIEPHDNFJAEOCDKAA.stefan.roese@esd-electronics.com
Stefan Roese wrote:
>>Is arch/ppc/kernel/ppc4xx_serial.c of any relevance any more? It
>>doesn't include any code unless CONFIG_DEBUG_BRINGUP is defined, and
>>it doesn't look like it would compile, let alone be called, if it was
>>defined.
>>
>
> That was also my impression. It seems, that this file could be removed.
>
> Stefan.
>
>
>
>
>
remnance from the intial release.
--armin
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-02-14 8:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-14 5:30 ppc4xx_serial.c? David Gibson
2002-02-14 8:46 ` ppc4xx_serial.c? Stefan Roese
2002-02-14 8:06 ` Armin [this message]
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=3C6B6FE9.6030406@pacbell.net \
--to=akuster@pacbell.net \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=stefan.roese@esd-electronics.com \
/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).