linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Rune Torgersen <runet@innovsys.com>
Cc: Tom Rini <trini@kernel.crashing.org>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: Broken arch/ppc/8260_io/uart.c
Date: Sun, 20 Jun 2004 07:10:35 +0100	[thread overview]
Message-ID: <1087711835.4230.19.camel@localhost.localdomain> (raw)
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B06DB07@ismail.innsys.innovsys.com>


On Thu, 2004-06-17 at 14:24 -0500, Rune Torgersen wrote:
> The following patch broke compilation of uart.c for cases when SMC2 is
> not used
> (used to be doen by #define USE_SMC2 0, now is done by #undef USE_SMC2)

Please test the new driver instead.

--
dwmw2


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

      reply	other threads:[~2004-06-20  6:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-17 19:24 Broken arch/ppc/8260_io/uart.c Rune Torgersen
2004-06-20  6:10 ` David Woodhouse [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=1087711835.4230.19.camel@localhost.localdomain \
    --to=dwmw2@infradead.org \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=runet@innovsys.com \
    --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 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).