linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Olof Johansson <olof@lixom.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	paulus@samba.org, arnd@arndb.de,
	ppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: [POWERPC] iSeries has no legacy I/O
Date: Tue, 26 Sep 2006 07:32:34 +0200	[thread overview]
Message-ID: <20060926053234.GA27474@aepfle.de> (raw)
In-Reply-To: <20060926000616.5ece9149@pb15>

On Tue, Sep 26, Olof Johansson wrote:

> This will break floppy and 8042 on platforms that previously did not
> define it and relied on the default being that it was allowed. I'm not
> sure which ones that would be?  Getting it in early would give us
> plenty of time to deal with fallout, if any.

chrp32 and prep at least.

      reply	other threads:[~2006-09-26  5:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-26  3:57 [POWERPC] iSeries has no legacy I/O Stephen Rothwell
2006-09-26  5:06 ` Olof Johansson
2006-09-26  5:32   ` Olaf Hering [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=20060926053234.GA27474@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=arnd@arndb.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=olof@lixom.net \
    --cc=paulus@samba.org \
    --cc=sfr@canb.auug.org.au \
    /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).