From: Christoph Hellwig <hch@lst.de>
To: Paul Mackerras <paulus@samba.org>
Cc: akpm@osdl.org, linuxppc-dev@ozlabs.org, linuxppc64-dev@ozlabs.org
Subject: Re: powerpc.git tree now on kernel.org
Date: Wed, 16 Nov 2005 09:24:56 +0100 [thread overview]
Message-ID: <20051116082456.GA24802@lst.de> (raw)
In-Reply-To: <17274.51251.591579.8751@cargo.ozlabs.ibm.com>
On Wed, Nov 16, 2005 at 04:48:35PM +1100, Paul Mackerras wrote:
> Although some of these patches may go to Linus before 2.6.15 is
> released, I won't be asking Linus to pull this tree directly, since it
> is likely to get a bit messy as patches are updated. I expect that
> Andrew Morton will pull this tree periodically and include it in his
> -mm releases.
Please make sure at least all patches required to kill arch/ppc64 and
include/asm-ppc64 go to Linus. If 2.6.15 released with the include3
hack that would mean endless pain to people building external modules
and the distributions trying to support that.
next prev parent reply other threads:[~2005-11-16 8:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 5:48 powerpc.git tree now on kernel.org Paul Mackerras
2005-11-16 6:17 ` Fwd: " Kumar Gala
2005-11-16 8:24 ` Christoph Hellwig [this message]
2005-11-16 8:31 ` Paul Mackerras
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=20051116082456.GA24802@lst.de \
--to=hch@lst.de \
--cc=akpm@osdl.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).