All of lore.kernel.org
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: mvebu: change order of ethernet DT nodes on Armada 38x
Date: Wed, 24 Feb 2016 22:33:50 +0000	[thread overview]
Message-ID: <20160224223350.GP19428@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20160224184114.GB2292@1wt.eu>

On Wed, Feb 24, 2016 at 07:41:14PM +0100, Willy Tarreau wrote:
> Hi Russell,
> Well, now I'm one of these and I confirm that it's really painful to
> have a different ordering between the DTB provided in mainline and the
> DTB provided with the board. The worst thing is that using mainline,
> eth0 corresponds to the switch and appears up, so you don't immediately
> realize that it's not where your cable is connected :-/
> 
> Thus could we please get Thomas' patch to ensure that the board boots
> with similar interface naming with both the original and mainline kernel ?

I didn't say no to it, I merely asked a few pertinent questions and
made some pertinent points.

Let me restate:

* Today, people who switch between mainline and vendor kernels
  experience some pain due to the NIC order changing.

* Mainline has had support for Armada 38x for 2 years now, which is
  long enough for it to have gained users.  AFAICS, there haven't been
  any complaints about the different NIC ordering.  Changing the NIC
  ordering is going to cause breakage to these users when they migrate
  across the change.

By making the change, we're effectively telling these mainline-only
users "we don't care about your setups, we're going to break them"
because that's exactly what we're going to do.

Of course, if no one complains about the change, you've got away
with it.

I think the folk who want to make this change should be prepared for
userspace breakage reports: Linus feels very strongly about zero
userspace regressions, as we all should know.

What I'm saying, therefore, is make the change, but if you have one
report that someone's userspace setup has broken as a result of the
change, the change must be reverted.

-- 
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

  parent reply	other threads:[~2016-02-24 22:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27 15:08 [PATCH 0/2] ARM: mvebu: network interface naming Thomas Petazzoni
2016-01-27 15:08 ` [PATCH 1/2] ARM: mvebu: change order of ethernet DT nodes on Armada 38x Thomas Petazzoni
2016-01-27 19:31   ` Russell King - ARM Linux
2016-01-27 19:45     ` Willy Tarreau
2016-01-29 11:48       ` Russell King - ARM Linux
2016-02-03 14:56         ` Thomas Petazzoni
2016-02-24 18:41         ` Willy Tarreau
2016-02-24 19:02           ` Imre Kaloz
2016-02-24 19:07             ` Willy Tarreau
2016-02-25 10:32             ` Thomas Petazzoni
2016-02-24 22:33           ` Russell King - ARM Linux [this message]
2016-02-24 22:56             ` Willy Tarreau
2016-02-25 10:36             ` Thomas Petazzoni
2016-02-25 13:48               ` Imre Kaloz
2016-02-25 10:31           ` Thomas Petazzoni
2016-02-25 10:40             ` Willy Tarreau
2016-01-27 15:08 ` [PATCH 2/2] ARM: mvebu: add reference to ETH connectors for A385-AP Thomas Petazzoni
2016-02-08 14:48 ` [PATCH 0/2] ARM: mvebu: network interface naming Gregory CLEMENT

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=20160224223350.GP19428@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.