From: Roman Zippel <zippel@linux-m68k.org>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: [PATCH 0/7] apus updates for 2.6
Date: Tue, 25 May 2004 03:35:31 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.58.0405250333320.13079@scrub.local> (raw)
In-Reply-To: <16562.40439.148880.532500@cargo.ozlabs.ibm.com>
Hi,
On Tue, 25 May 2004, Paul Mackerras wrote:
> > Following are some patches to get APUS closer to working in 2.6. These are
> > the simpler patches, other patches will follow later (of which are not
> > that much left, but may need a bit more work).
>
> So, do you think these should go upstream to Andrew Morton?
Yes, unless there are any objections. Who should send them to Andrew?
bye, Roman
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-05-25 1:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-25 0:27 [PATCH 0/7] apus updates for 2.6 Roman Zippel
2004-05-25 1:14 ` Paul Mackerras
2004-05-25 1:35 ` Roman Zippel [this message]
2004-05-25 2:33 ` Paul Mackerras
2004-05-25 7:53 ` Roman Zippel
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=Pine.LNX.4.58.0405250333320.13079@scrub.local \
--to=zippel@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.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