From: jamie@jamieiles.com (Jamie Iles)
To: linux-arm-kernel@lists.infradead.org
Subject: Merging Cadence macb/gem patches
Date: Tue, 13 Sep 2011 13:56:10 +0100 [thread overview]
Message-ID: <20110913125610.GE2781@pulham.picochip.com> (raw)
In-Reply-To: <20110830103655.GE5414@pulham.picochip.com>
On Tue, Aug 30, 2011 at 11:36:55AM +0100, Jamie Iles wrote:
> Hi Arnd,
>
> I have a series of patches[1] to add support for the Cadence GEM
> Ethernet MAC to the macb driver. A while back, DaveM said that he would
> be happy for these to go through an ARM tree[2], so would you pull these
> into the arm-soc tree?
>
> At the moment my patches are based on 3.1-rc1, but since then the
> drivers have been moved about and git merge doesn't seem to resolve
> this, so should I base them on the commit that moved them from the
> netdev tree? I'm not sure how to handle this.
Hi Arnd,
Would you be able to take these if I send you a pull request please?
Thanks,
Jamie
next prev parent reply other threads:[~2011-09-13 12:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 10:36 Merging Cadence macb/gem patches Jamie Iles
2011-09-13 12:56 ` Jamie Iles [this message]
2011-09-13 13:56 ` Arnd Bergmann
2011-09-13 16:38 ` David Miller
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=20110913125610.GE2781@pulham.picochip.com \
--to=jamie@jamieiles.com \
--cc=linux-arm-kernel@lists.infradead.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).