public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ralph Sennhauser <ralph.sennhauser@gmail.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	Gregory CLEMENT <gregory.clement@free-electrons.com>,
	Ralph Sennhauser <ralph.sennhauser@gmail.com>
Subject: [Regression?] Commit cb4f71c429 deliberately changes order of network interfaces
Date: Sun, 21 Aug 2016 15:11:58 +0200	[thread overview]
Message-ID: <20160821151158.78da01e6@gmail.com> (raw)

Dear List, Thomas, Gregory

Commit cb4f71c4298853db0c6751b1209e4535956f136c changes the order of
the network interfaces for armada-38x. As a special exception to the
"order by register address" rule says the comment in the dtsi. The
commit messages even calls it a violation.

I can't remember having owned a device were the internal and external
numbering actually matched, so the important bit for me is whatever the
order is it should remain constant.

Distributions like OpenWrt have to fix their code when moving from 4.4
currently to past 4.6 [1]. Worse the so called "wrong ordering" is
actually documented [2]. There are likely more victims out there. In
case it goes unnoticed by the distribution the users lan becomes wan
and vice versa.

It's unfortunate that this commit is already in stable 4.6 and 4.7.

What is your take on this? Should the commit be reverted?

Regards
Ralph

[1]
https://github.com/openwrt/openwrt/blob/master/target/linux/mvebu/base-files/etc/board.d/02_network
[2] https://wiki.openwrt.org/toh/linksys/wrt1x00ac_series#switch_layout

             reply	other threads:[~2016-08-21 13:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-21 13:11 Ralph Sennhauser [this message]
2016-08-24 14:50 ` [Regression?] Commit cb4f71c429 deliberately changes order of network interfaces Thomas Petazzoni
2016-08-24 16:19   ` Lennart Sorensen
2016-08-24 16:43     ` Thomas Petazzoni
2016-08-24 17:10       ` Lennart Sorensen
2016-08-24 18:38         ` Lennart Sorensen
2016-08-24 17:10   ` Ralph Sennhauser
2016-08-24 18:07     ` Lennart Sorensen
2016-08-24 18:14       ` Thomas Petazzoni
2016-08-24 18:27         ` Lennart Sorensen
2016-08-24 19:52           ` Thomas Petazzoni
2016-08-24 20:51             ` Lennart Sorensen
2016-08-24 18:15     ` Thomas Petazzoni
2016-08-24 20:41       ` Ralph Sennhauser
2016-08-24 21:48         ` Jason Cooper
2016-08-25  7:38           ` Ralph Sennhauser
2016-08-25 19:40             ` Lennart Sorensen
2016-08-26  8:43             ` Gregory CLEMENT
2016-08-26 10:39               ` Ralph Sennhauser

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=20160821151158.78da01e6@gmail.com \
    --to=ralph.sennhauser@gmail.com \
    --cc=gregory.clement@free-electrons.com \
    --cc=linux-kernel@vger.kernel.org \
    --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