From: David Miller <davem@davemloft.net>
To: vivien.didelot@savoirfairelinux.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@savoirfairelinux.com, andrew@lunn.ch,
f.fainelli@gmail.com
Subject: Re: [PATCH net-next 0/3] net: dsa: mv88e6xxx: cleanup Global Control 2 register
Date: Thu, 10 May 2018 16:13:10 -0400 (EDT) [thread overview]
Message-ID: <20180510.161310.1711109503750888571.davem@davemloft.net> (raw)
In-Reply-To: <20180509153851.10207-1-vivien.didelot@savoirfairelinux.com>
From: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Date: Wed, 9 May 2018 11:38:48 -0400
> The mv88e6xxx driver still writes arbitrary values in the Global 1
> Control 2 register at setup, which layout differs a lot between chips.
> This results in an inconsistent configuration, for example with the
> Remote Management Unit (RMU).
>
> The first patch adds an operation for the Cascade Port bits, the second
> patch sets the device number in the device mapping function and the
> third patch adds an operation to correctly disable the RMU.
Series applied.
prev parent reply other threads:[~2018-05-10 20:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 15:38 [PATCH net-next 0/3] net: dsa: mv88e6xxx: cleanup Global Control 2 register Vivien Didelot
2018-05-09 15:38 ` [PATCH net-next 1/3] net: dsa: mv88e6xxx: add a cascade port op Vivien Didelot
2018-05-09 19:05 ` Andrew Lunn
2018-05-09 15:38 ` [PATCH net-next 2/3] net: dsa: mv88e6xxx: set device number Vivien Didelot
2018-05-09 19:06 ` Andrew Lunn
2018-05-09 15:38 ` [PATCH net-next 3/3] net: dsa: mv88e6xxx: add RMU disable op Vivien Didelot
2018-05-09 19:08 ` Andrew Lunn
2018-05-10 20:13 ` David Miller [this message]
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=20180510.161310.1711109503750888571.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=kernel@savoirfairelinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.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).