From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Jon Smirl" <jonsmirl@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linuxppc-dev@ozlabs.org, linux-next@vger.kernel.org,
Paul Mackerras <paulus@samba.org>,
Jean Delvare <khali@linux-fr.org>,
Timur Tabi <timur@freescale.com>
Subject: Re: linux-next: manual merge of the powerpc tree
Date: Thu, 3 Jul 2008 23:54:26 -0600 [thread overview]
Message-ID: <fa686aa40807032254j76dd1892y7af76c1a2d555809@mail.gmail.com> (raw)
In-Reply-To: <20080703152453.GB2284@secretlab.ca>
On Thu, Jul 3, 2008 at 9:24 AM, Grant Likely <grant.likely@secretlab.ca> wrote:
> On Thu, Jul 03, 2008 at 08:22:18AM -0400, Jon Smirl wrote:
>> Testing was good when the patch was initially posted in January. In
>> the last six months the initial patch set has been sliced and diced
>> into a bunch of different pieces but the contents of this patch are
>> essentially unchanged.
>>
>> I don't care which tree it uses to get to mainline, I'd just like to
>> see it get merged.
>
> Me too, but it is used by some of the mpc8xxx platforms too, so I'd like
> to see an ack from one of those users also.
Okay, I've tested it on my board. All looks good to me. I'd prefer
to hear back from one of the Freescale folks, but on a second reading
I think it is pretty safe. I'll make sure any merge conflicts are
resolved.
Jean, is it okay with you to drop it from your tree and merge it through mine?
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-07-04 5:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 3:39 linux-next: manual merge of the powerpc tree Stephen Rothwell
2008-07-03 5:47 ` Grant Likely
2008-07-03 12:22 ` Jon Smirl
2008-07-03 15:24 ` Grant Likely
2008-07-04 5:54 ` Grant Likely [this message]
2008-07-04 7:35 ` Jean Delvare
-- strict thread matches above, loose matches on Subject: below --
2008-10-14 1:02 Stephen Rothwell
2008-10-14 1:02 Stephen Rothwell
2008-07-14 5:44 Stephen Rothwell
2008-07-15 1:24 ` Steven Rostedt
2008-07-07 13:07 Stephen Rothwell
2008-07-07 21:13 ` Daniel Walker
2008-07-11 19:01 ` Bartlomiej Zolnierkiewicz
2008-07-12 3:41 ` Benjamin Herrenschmidt
2008-07-01 6:48 Stephen Rothwell
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=fa686aa40807032254j76dd1892y7af76c1a2d555809@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=jonsmirl@gmail.com \
--cc=khali@linux-fr.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
--cc=timur@freescale.com \
/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).