netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jason@lakedaemon.net
Cc: thomas.petazzoni@free-electrons.com, netdev@vger.kernel.org,
	alior@marvell.com, jochen.armkernel@leahnim.org,
	simon.guinot@sequanux.org, ryan@presslab.us,
	vdonnefort@lacie.com, ethan@ethantuttle.com,
	stable@vger.kernel.org, ezequiel.garcia@free-electrons.com,
	yves@cheny.fr, gregory.clement@free-electrons.com,
	psanford@nearbuy.io, w@1wt.eu,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] net: mvneta: properly disable HW PHY polling and ensure adjust_link() works
Date: Thu, 05 Sep 2013 14:51:13 -0400 (EDT)	[thread overview]
Message-ID: <20130905.145113.3434775203310652.davem@davemloft.net> (raw)
In-Reply-To: <20130904145051.GO19598@titan.lakedaemon.net>

From: Jason Cooper <jason@lakedaemon.net>
Date: Wed, 4 Sep 2013 10:50:51 -0400

> On Wed, Sep 04, 2013 at 04:21:18PM +0200, Thomas Petazzoni wrote:
>> This commit fixes a long-standing bug that has been reported by many
>> users: on some Armada 370 platforms, only the network interface that
>> has been used in U-Boot to tftp the kernel works properly in
>> Linux. The other network interfaces can see a 'link up', but are
>> unable to transmit data. The reports were generally made on the Armada
>> 370-based Mirabox, but have also been given on the Armada 370-RD
>> board.
 ...
> 
> David,
> 
> Offending patch is:
> 
>   c5aff18 net: mvneta: driver for Marvell Armada 370/XP network unit
> 
> Applies and builds cleanly against v3.8.13, v3.9.11, v3.10.10, and v3.11
> 
> Acked-by: Jason Cooper <jason@lakedaemon.net>

Applied.

  parent reply	other threads:[~2013-09-05 18:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04 14:21 [PATCH] net: mvneta: properly disable HW PHY polling and ensure adjust_link() works Thomas Petazzoni
2013-09-04 14:50 ` Jason Cooper
2013-09-04 15:20   ` Vincent Donnefort
2013-09-04 16:00     ` yves
2013-09-05 18:51   ` David Miller [this message]
2013-09-04 16:08 ` Gregory CLEMENT
2013-09-04 16:32 ` Willy Tarreau
2013-09-05  4:14   ` Ethan Tuttle
2013-09-05  5:12     ` Willy Tarreau
2013-09-05  5:22       ` Ethan Tuttle
2013-09-05  6:23         ` yves
2013-09-05  6:40           ` Willy Tarreau
2013-09-05  6:52             ` Ethan Tuttle
2013-09-05  7:28       ` Thomas Petazzoni
2013-09-05  7:44         ` Willy Tarreau
2013-09-05  8:26           ` Thomas Petazzoni
2013-09-05  9:11             ` Willy Tarreau
2013-09-05  9:24               ` Thomas Petazzoni
2013-09-05 11:38             ` Jason Cooper
2013-09-05 11:36         ` 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=20130905.145113.3434775203310652.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=alior@marvell.com \
    --cc=ethan@ethantuttle.com \
    --cc=ezequiel.garcia@free-electrons.com \
    --cc=gregory.clement@free-electrons.com \
    --cc=jason@lakedaemon.net \
    --cc=jochen.armkernel@leahnim.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=netdev@vger.kernel.org \
    --cc=psanford@nearbuy.io \
    --cc=ryan@presslab.us \
    --cc=simon.guinot@sequanux.org \
    --cc=stable@vger.kernel.org \
    --cc=thomas.petazzoni@free-electrons.com \
    --cc=vdonnefort@lacie.com \
    --cc=w@1wt.eu \
    --cc=yves@cheny.fr \
    /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).