From: Aurelien Jarno <aurelien@aurel32.net>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Andrew Morton <akpm@osdl.org>,
linux-mips@linux-mips.org, Michael Buesch <mb@bu3sch.de>,
Felix Fietkau <nbd@openwrt.org>,
Florian Schirmer <jolt@tuxbox.org>
Subject: Re: [PATCH -mm 0/4] MIPS BCM947xx CPUs support
Date: Tue, 07 Aug 2007 15:22:32 +0200 [thread overview]
Message-ID: <46B87218.1080704@aurel32.net> (raw)
In-Reply-To: <20070807131447.GA24212@linux-mips.org>
Ralf Baechle a écrit :
> On Tue, Aug 07, 2007 at 03:09:50PM +0200, Aurelien Jarno wrote:
>
>> I don't see a patch corresponding to the MIPS tree in the broken-out
>> directory. Anyway what other solution do you propose? I can see:
>
> There isn't because until -rc2 everything went straight to Linus. The
> next -mm should have a git-mips patch again.
>
>> - Integrate the patches that have the most risk of conflicts (I think
>> patch #1) into the MIPS tree.
>> - Integrate all BCM947xx patches into the MIPS tree accepting that it
>> can compile without additional patches.
>> - Integrate SSB patches into the MIPS tree.
>
> I can do that if Andrew is ok with it?
Well that was actually three different ways to go.
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' aurel32@debian.org | aurelien@aurel32.net
`- people.debian.org/~aurel32 | www.aurel32.net
next prev parent reply other threads:[~2007-08-07 13:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 15:07 [PATCH -mm 0/4] MIPS BCM947xx CPUs support Aurelien Jarno
2007-08-07 12:55 ` Ralf Baechle
2007-08-07 13:09 ` Aurelien Jarno
2007-08-07 13:14 ` Ralf Baechle
2007-08-07 13:22 ` Aurelien Jarno [this message]
2007-08-07 13:13 ` Michael Buesch
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=46B87218.1080704@aurel32.net \
--to=aurelien@aurel32.net \
--cc=akpm@osdl.org \
--cc=jolt@tuxbox.org \
--cc=linux-mips@linux-mips.org \
--cc=mb@bu3sch.de \
--cc=nbd@openwrt.org \
--cc=ralf@linux-mips.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.