From: David Miller <davem@davemloft.net>
To: b.brezillon@overkiz.com
Cc: nicolas.ferre@atmel.com, rob.herring@calxeda.com,
pawel.moll@arm.com, mark.rutland@arm.com, swarren@wwwdotorg.org,
ian.campbell@citrix.com, linux@arm.linux.org.uk,
f.fainelli@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 0/2] net/cadence/macb: add support for dt phy definition
Date: Tue, 27 Aug 2013 12:41:36 -0400 (EDT) [thread overview]
Message-ID: <20130827.124136.926975779215612126.davem@davemloft.net> (raw)
In-Reply-To: <521CD61C.8010103@overkiz.com>
From: boris brezillon <b.brezillon@overkiz.com>
Date: Tue, 27 Aug 2013 18:38:52 +0200
> On 27/08/2013 18:20, David Miller wrote:
>> From: boris brezillon <b.brezillon@overkiz.com>
>> Date: Tue, 27 Aug 2013 09:42:34 +0200
>>
>>> Could you apply, the 3rd version of this series instead ?
>> There can never be an "instead" or reverting patches I've said I've
>> applied already.
>>
>> If you want changes, you have to submit follow-on fixes.
>
> Hello David,
>
> I sent the incremental patches based on your net-next branch:
> https://lkml.org/lkml/2013/8/27/257
> https://lkml.org/lkml/2013/8/27/259
The place to check to see if your patch is queued up is here:
http://patchwork.ozlabs.org/project/netdev/list/
If it's there, it's not necessary to notify me of anything.
prev parent reply other threads:[~2013-08-27 16:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1377186980-21902-1-git-send-email-b.brezillon@overkiz.com>
2013-08-26 20:04 ` [PATCH 0/2] net/cadence/macb: add support for dt phy definition David Miller
2013-08-27 7:42 ` boris brezillon
2013-08-27 9:07 ` Florian Fainelli
2013-08-27 9:13 ` boris brezillon
2013-08-27 9:16 ` Nicolas Ferre
2013-08-27 16:20 ` David Miller
2013-08-27 16:38 ` boris brezillon
2013-08-27 16:41 ` David Miller [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=20130827.124136.926975779215612126.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=b.brezillon@overkiz.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=ian.campbell@citrix.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=swarren@wwwdotorg.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).