LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kumar Gala <galak@gate.crashing.org>
Cc: linuxppc-dev@ozlabs.org, linuxppc64-dev@ozlabs.org
Subject: Re: [PATCH] powerpc: Call find_legacy_serial_ports() if we enable CONFIG_SERIAL_8250
Date: Wed, 21 Dec 2005 16:13:30 +1100	[thread overview]
Message-ID: <20051221161330.1a23384b.sfr@canb.auug.org.au> (raw)
In-Reply-To: <Pine.LNX.4.44.0512202045040.1835-100000@gate.crashing.org>

[-- Attachment #1: Type: text/plain, Size: 999 bytes --]

On Tue, 20 Dec 2005 20:45:27 -0600 (CST) Kumar Gala <galak@gate.crashing.org> wrote:
>
> In setup_arch and setup_system call find_legacy_serial_ports() if we
> build in support for 8250 serial ports instead of basing it on PPC_MULTIPLATFORM.
> 
> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
> 
> ---
> commit 399e10aa1c6a3ca64e8e8e8cea7289e9908cc62c
> tree 3e5320b8a97a37c4d010186aabf8a95e5be264b4
> parent 7b69a37a4e811e72e82896ab38e6ae04542455f5
> author Kumar Gala <galak@kernel.crashing.org> Tue, 20 Dec 2005 20:48:36 -0600
> committer Kumar Gala <galak@kernel.crashing.org> Tue, 20 Dec 2005 20:48:36 -0600
> 
>  arch/powerpc/kernel/setup_32.c |    2 +-
>  arch/powerpc/kernel/setup_64.c |    2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)

You should probably change the Makefile as well to build legacy_serial.c
in the CONFIG_SERIAL_8250 case.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-12-21  5:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-21  2:45 [PATCH] powerpc: Call find_legacy_serial_ports() if we enable CONFIG_SERIAL_8250 Kumar Gala
2005-12-21  5:13 ` Stephen Rothwell [this message]
2005-12-21 15:31   ` Kumar Gala

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=20051221161330.1a23384b.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=galak@gate.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxppc64-dev@ozlabs.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