public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Porter <porter@cox.net>
To: davidm@hpl.hp.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: can we drop early_serial_setup()?
Date: Sat, 21 Sep 2002 06:45:04 -0700	[thread overview]
Message-ID: <20020921064504.A31995@home.com> (raw)
In-Reply-To: <15755.44527.146016.975532@napali.hpl.hp.com>; from davidm@napali.hpl.hp.com on Fri, Sep 20, 2002 at 04:23:27PM -0700

On Fri, Sep 20, 2002 at 04:23:27PM -0700, David Mosberger wrote:
> >>>>> On Fri, 20 Sep 2002 16:33:57 -0700, Matt Porter <porter@cox.net> said:
> 
>   Matt> serial8250_ports and serial8250_pops are not static structs
>   Matt> in your tree?
> 
> It is.  The new routine (early_register_port) goes into 8250.c, so that's
> fine.

That will be fine then.  I misconstrued your first statements as
indicating that we should duplicate this code in each arch (which
I didn't like).  As far as PPC is concerned, go ahead and wipe
out early_serial_setup when you bring in early_register_port.

FWIW, there's actually been more PPC platforms than ev64260 using
early_serial_setup. They had abandoned it temporarily for a less
flexible approach due to the breakage.

Thanks,
-- 
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.

  reply	other threads:[~2002-09-21 13:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-20  4:59 can we drop early_serial_setup()? David Mosberger
2002-09-20 23:33 ` Matt Porter
2002-09-20 23:23   ` David Mosberger
2002-09-21 13:45     ` Matt Porter [this message]
2002-09-23 19:02       ` David Mosberger
2002-09-23 22:44 ` Mark A. Greer

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=20020921064504.A31995@home.com \
    --to=porter@cox.net \
    --cc=davidm@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.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