All of lore.kernel.org
 help / color / mirror / Atom feed
From: kaloz@openwrt.org (Imre Kaloz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: mvebu: change order of ethernet DT nodes on Armada 38x
Date: Thu, 25 Feb 2016 14:48:16 +0100	[thread overview]
Message-ID: <op.ydd5yqmx2s3iss@ecaz> (raw)
In-Reply-To: <20160225113610.351149bf@free-electrons.com>

On Thu, 25 Feb 2016 11:36:10 +0100, Thomas Petazzoni  
<thomas.petazzoni@free-electrons.com> wrote:

> Hello,
>
> On Wed, 24 Feb 2016 22:33:50 +0000, Russell King - ARM Linux wrote:
>
>> 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 agree with you that the change isn't perfect, it's really a matter of
> trade-off. The perfect change would be to be able to help the network
> subsystem in its naming of network interfaces, but this has always been
> rejected. It would have indeed been better to add this DT node ordering
> work-around earlier, but we didn't do it, and we're in the present.
>
> So again, yes the proposed change is not "great", but I believe it's
> relatively reasonable. If we indeed get feedback that it's breaking
> things for too many people, I guess we'll just revert. I don't mind if
> things remain as they are today, i.e with a weird ordering of the
> network interfaces. It's just annoying for new people using the
> platform, but it's not horrible either.

I can check during the weekend if the mainlined Linksys boards get broken  
because of this.


Imre

  reply	other threads:[~2016-02-25 13:48 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
2016-02-24 22:56             ` Willy Tarreau
2016-02-25 10:36             ` Thomas Petazzoni
2016-02-25 13:48               ` Imre Kaloz [this message]
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=op.ydd5yqmx2s3iss@ecaz \
    --to=kaloz@openwrt.org \
    --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.