From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: EMAC patches
Date: Wed, 24 Sep 2008 07:14:41 +1000 [thread overview]
Message-ID: <1222204481.8277.10.camel@pasglop> (raw)
In-Reply-To: <20080923123520.GB10837@yoda.jdub.homelinux.org>
On Tue, 2008-09-23 at 08:35 -0400, Josh Boyer wrote:
> Hi Ben,
>
> What's your plan for the existing set of EMAC patches? I'm just curious if
> you plan to send them through my tree (Jeff acked my set), or if you are
> going to ask Jeff to pull them into his.
>
> I could keep an emac branch in my git tree based on whatever you think is
> best without much effort if that would help you at all. If not, I just
> need to sort out how to land all the pieces for various board ports at one
> time.
Stick them in a branch in your tree, and if you can also pickup the
pending ones from AMCC that would be great !
Thanks,
Ben.
prev parent reply other threads:[~2008-09-23 21:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 12:35 EMAC patches Josh Boyer
2008-09-23 21:14 ` Benjamin Herrenschmidt [this message]
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=1222204481.8277.10.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.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).