From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: David Miller <davem@davemloft.net>, antoine.tenart@free-electrons.com
Cc: alexandre.belloni@free-electrons.com,
thomas.petazzoni@free-electrons.com, zmxu@marvell.com,
jszhang@marvell.com, netdev@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 00/10] ARM: Berlin: Ethernet support
Date: Wed, 01 Oct 2014 00:01:53 +0200 [thread overview]
Message-ID: <542B2851.2050705@gmail.com> (raw)
In-Reply-To: <20140930.163735.2099691931550261883.davem@davemloft.net>
On 30.09.2014 22:37, David Miller wrote:
> From: Antoine Tenart <antoine.tenart@free-electrons.com>
> Date: Tue, 30 Sep 2014 16:28:06 +0200
>
>> This series introduce support for the Ethernet controller on Berlin SoCs,
>> using the existing pxa168 Ethernet driver. In order to do this, DT
>> support is added to the driver alongside some other modifications and
>> fixes.
>>
>> This has been tested on a Berlin BG2Q DMP board.
>
> Applied to net-next, thanks.
David,
usually I'd prefer to take the dts patches through berlin and arm-soc
tree, _but_ as they are touching berlin stuff only I am fine with you
taking them, too.
Just to make sure how long I have to take care of potential merge
issues, is your current net-next meant for v3.18 or v3.19?
Sebastian
next prev parent reply other threads:[~2014-09-30 22:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 14:28 [PATCH v6 00/10] ARM: Berlin: Ethernet support Antoine Tenart
2014-09-30 14:28 ` [PATCH v6 01/10] net: pxa168_eth: clean up Antoine Tenart
2014-09-30 14:28 ` [PATCH v6 02/10] net: pxa168_eth: add device tree support Antoine Tenart
2014-09-30 14:28 ` [PATCH v6 03/10] Documentation: bindings: net: add the Marvell PXA168 Ethernet controller Antoine Tenart
2014-09-30 14:28 ` [PATCH v6 04/10] net: pxa168_eth: fix Ethernet flow control status Antoine Tenart
[not found] ` <1412087296-18475-1-git-send-email-antoine.tenart-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2014-09-30 14:28 ` [PATCH v6 05/10] net: pxa168_eth: set the mac address on the Ethernet controller Antoine Tenart
2014-09-30 14:28 ` [PATCH v6 06/10] net: pxa168_eth: rework the MAC address setup Antoine Tenart
2014-09-30 14:28 ` [PATCH v6 07/10] net: pxa168_eth: allow Berlin SoCs to use the pxa168_eth driver Antoine Tenart
2014-09-30 14:28 ` [PATCH v6 08/10] net: pxa168_eth: allow to compile the pxa168_eth driver for tests Antoine Tenart
2014-09-30 14:28 ` [PATCH v6 09/10] ARM: dts: berlin: add the Ethernet node Antoine Tenart
2014-09-30 14:28 ` [PATCH v6 10/10] ARM: dts: berlin: enable the Ethernet port on the BG2Q DMP Antoine Tenart
2014-09-30 20:37 ` [PATCH v6 00/10] ARM: Berlin: Ethernet support David Miller
2014-09-30 22:01 ` Sebastian Hesselbarth [this message]
2014-09-30 23:59 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2014-09-26 14:33 Antoine Tenart
2014-09-26 14:37 ` Antoine Tenart
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=542B2851.2050705@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=antoine.tenart@free-electrons.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=jszhang@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=thomas.petazzoni@free-electrons.com \
--cc=zmxu@marvell.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).