From: Andrew Lunn <andrew@lunn.ch>
To: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@savoirfairelinux.com,
"David S. Miller" <davem@davemloft.net>,
Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: [PATCH net-next 0/5] net: dsa: mv88e6xxx: move registers macros
Date: Fri, 2 Jun 2017 23:16:47 +0200 [thread overview]
Message-ID: <20170602211647.GA28084@lunn.ch> (raw)
In-Reply-To: <20170602210619.26837-1-vivien.didelot@savoirfairelinux.com>
On Fri, Jun 02, 2017 at 05:06:14PM -0400, Vivien Didelot wrote:
> This patchset brings no functional changes.
>
> It is the first step of a cleanup renaming the chip header file and
> moving the Register definitions _as is_ in their proper header files.
>
> A following patchset will prefix them with the appropriate model
> (MV88E6XXX_ or e.g. MV88E6390_) to respect an implicit namespace and
> easily identify model subtleties in registers layout, as correctly done
> in the newly added serdes.h header.
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2017-06-02 21:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 21:06 [PATCH net-next 0/5] net: dsa: mv88e6xxx: move registers macros Vivien Didelot
2017-06-02 21:06 ` [PATCH net-next 1/5] net: dsa: mv88e6xxx: rename chip header Vivien Didelot
2017-06-02 21:06 ` [PATCH net-next 2/5] net: dsa: mv88e6xxx: move PHY macros Vivien Didelot
2017-06-02 21:06 ` [PATCH net-next 3/5] net: dsa: mv88e6xxx: move the Port macros Vivien Didelot
2017-06-02 21:06 ` [PATCH net-next 4/5] net: dsa: mv88e6xxx: move the Global 1 macros Vivien Didelot
2017-06-02 21:06 ` [PATCH net-next 5/5] net: dsa: mv88e6xxx: move the Global 2 macros Vivien Didelot
2017-06-02 21:16 ` Andrew Lunn [this message]
2017-06-05 0:08 ` [PATCH net-next 0/5] net: dsa: mv88e6xxx: move registers macros David Miller
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=20170602211647.GA28084@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--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).