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: Tue, 1 Nov 2005 06:22:50 -0700 [thread overview]
Message-ID: <20051101062250.A28639@cox.net> (raw)
In-Reply-To: <17255.737.832440.137041@cargo.ozlabs.ibm.com>; from paulus@samba.org on Tue, Nov 01, 2005 at 04:53:37PM +1100
On Tue, Nov 01, 2005 at 04:53:37PM +1100, Paul Mackerras wrote:
> Matt Porter writes:
>
> > 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?
>
> Did you send them yet? Linus has pulled the powerpc-merge tree, as
> I'm sure you've noticed.
Yes I did. I saw the merge go into mainline and rebased what was
necessary off of that. Andrew now has them queued up for Linus so
we are set. BTW, we're starting to look at merging 4xx to arch/powerpc/
now.
-Matt
next prev parent reply other threads:[~2005-11-01 13:22 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
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 [this message]
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=20051101062250.A28639@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 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).