netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: ezequiel.garcia@free-electrons.com
Cc: thomas.petazzoni@free-electrons.com, netdev@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, jason@lakedaemon.net,
	mw@semihalf.com, gregory.clement@free-electrons.com,
	tawfik@marvell.com, alior@marvell.com
Subject: Re: [PATCH 0/6] net: mvpp2: Assorted fixes
Date: Tue, 22 Jul 2014 19:52:22 -0700 (PDT)	[thread overview]
Message-ID: <20140722.195222.775371949777233094.davem@davemloft.net> (raw)
In-Reply-To: <20140722.174153.413669013449137654.davem@davemloft.net>

From: David Miller <davem@davemloft.net>
Date: Tue, 22 Jul 2014 17:41:53 -0700 (PDT)

> From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
> Date: Tue, 22 Jul 2014 20:20:04 -0300
> 
>> On 23 Jul 12:29 AM, Thomas Petazzoni wrote:
>>> On Tue, 22 Jul 2014 13:16:39 -0700 (PDT), David Miller wrote:
>>> 
>>> > >> This series does not apply to the 'net' tree at all, please respin
>>> > >> and resubmit.
>>> > > 
>>> > > This series applies on net-next.
>>> > > 
>>> > > Sorry for not mentioning it,
>>> > 
>>> > They are bonafide bug fixes, therefore should be targetted at 'net'.
>>> 
>>> Except that I believe they are fixes for a driver which itself is in
>>> net-next, i.e scheduled for 3.17.
>>> 
>> 
>> That's right. These are fixes for the new mvpp2 driver, which is only
>> in net-next.
> 
> Ok, I queued them back up, thanks for the clarification.

I've applied the 4 driver patches to net-next.  But, since the ARM
device tree file changes did not go into net-next, I can't apply the
last two patches to my tree.  You'll need to sort that out yourself.

It's a bit unfortunate that things are now out of sync like this, but
that's what you asked me to do.

  reply	other threads:[~2014-07-23  2:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-21 16:48 [PATCH 0/6] net: mvpp2: Assorted fixes Ezequiel Garcia
2014-07-21 16:48 ` [PATCH 1/6] net: mvpp2: Fix the periodic XON enable bit Ezequiel Garcia
2014-07-21 16:48 ` [PATCH 2/6] net: mvpp2: Enable proper PHY polling and fix port functionality Ezequiel Garcia
2014-07-21 16:48 ` [PATCH 3/6] net: mvpp2: Fix the BM pool buffer release check Ezequiel Garcia
2014-07-21 16:48 ` [PATCH 4/6] net: mvpp2: Simplify BM pool buffers freeing Ezequiel Garcia
2014-07-21 16:48 ` [PATCH 5/6] ARM: mvebu: Add ethernet aliases required by U-Boot Ezequiel Garcia
2014-07-21 16:48 ` [PATCH 6/6] ARM: mvebu: Add missing MDIO clock in Armada 375 Ezequiel Garcia
2014-07-22  3:27 ` [PATCH 0/6] net: mvpp2: Assorted fixes David Miller
2014-07-22 14:45   ` Ezequiel Garcia
2014-07-22 20:16     ` David Miller
2014-07-22 22:29       ` Thomas Petazzoni
2014-07-22 23:20         ` Ezequiel Garcia
2014-07-23  0:41           ` David Miller
2014-07-23  2:52             ` David Miller [this message]
2014-07-23 10:53               ` Ezequiel Garcia
2014-07-23 12:13 ` Jason Cooper

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=20140722.195222.775371949777233094.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=alior@marvell.com \
    --cc=ezequiel.garcia@free-electrons.com \
    --cc=gregory.clement@free-electrons.com \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mw@semihalf.com \
    --cc=netdev@vger.kernel.org \
    --cc=tawfik@marvell.com \
    --cc=thomas.petazzoni@free-electrons.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).