From: Matt Porter <mporter@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, linuxppc64-dev@ozlabs.org
Subject: Re: Patches for 2.6.15
Date: Fri, 28 Oct 2005 10:30:41 -0700 [thread overview]
Message-ID: <20051028103041.B15268@cox.net> (raw)
In-Reply-To: <17250.8725.358204.62510@cargo.ozlabs.ibm.com>; from paulus@samba.org on Fri, Oct 28, 2005 at 11:05:25PM +1000
On Fri, Oct 28, 2005 at 11:05:25PM +1000, Paul Mackerras wrote:
> If anyone has patches for arch/ppc{,64} and include/asm-ppc{,64} that
> they would like to see go upstream now that 2.6.14 is out, other than
> patches that are already in the powerpc-merge tree, please let me
> know. I am planning to ask Linus to pull the powerpc-merge tree
> shortly, and that will probably break your patches.
Ok, we have a set of 4xx patches that I plan to send to Andrew.
They are some existing 4xx SoC/board updates as well as a new
SoC/board. They are obviously mostly confined to the 4xx code paths
but there's likely conflicts in changes to Makefiles, etc.
Would you prefer these going upstream before or after the
powerpc-merge pull?
-Matt
next prev parent reply other threads:[~2005-10-28 17:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-28 13:05 Patches for 2.6.15 Paul Mackerras
2005-10-28 16:00 ` Christopher Friesen
2005-10-28 17:54 ` Andreas Schwab
2005-10-28 18:41 ` Kumar Gala
2005-10-29 0:10 ` Paul Mackerras
2005-10-28 17:30 ` Matt Porter [this message]
2005-10-28 18:44 ` Kumar Gala
2005-10-28 20:02 ` Andrew Morton
2005-10-29 0:20 ` Paul Mackerras
2005-10-29 0:40 ` Andrew Morton
2005-10-29 5:45 ` Paul Mackerras
2005-10-29 5:59 ` Andrew Morton
2005-11-01 5:53 ` Paul Mackerras
2005-11-01 13:22 ` Matt Porter
2005-10-28 18:49 ` Kumar Gala
2005-10-29 8:07 ` Stephen Rothwell
2005-10-29 12:55 ` galak
2005-11-01 5:57 ` Paul Mackerras
2005-10-28 23:11 ` Arnd Bergmann
2005-10-28 23:16 ` [PATCH] reserve syscall numbers for Cell Arnd Bergmann
2005-10-28 23:21 ` Patches for 2.6.15 Andrew Morton
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=20051028103041.B15268@cox.net \
--to=mporter@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.