From: David Miller <davem@davemloft.net>
To: vivien.didelot@savoirfairelinux.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@savoirfairelinux.com, f.fainelli@gmail.com,
andrew@lunn.ch
Subject: Re: [PATCH net-next v2 0/7] net: dsa: mv88e6xxx: ops cosmetics
Date: Fri, 09 Jun 2017 12:11:20 -0400 (EDT) [thread overview]
Message-ID: <20170609.121120.2149178729617274766.davem@davemloft.net> (raw)
In-Reply-To: <20170608223414.594-1-vivien.didelot@savoirfairelinux.com>
From: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Date: Thu, 8 Jun 2017 18:34:07 -0400
> This patchset brings no functional changes. It is a first step in a
> bigger cosmetics change to the driver. It simplifies print messages and
> polishes data types and chip operations.
>
> The next patchs will only prefix and document the port registers macros.
>
> Changes in v2:
> - KISS and simply use dev_* since chip->ds may not be initialized
> - add reviewers tags
Series applied, thank you.
prev parent reply other threads:[~2017-06-09 16:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 22:34 Vivien Didelot
2017-06-08 22:34 ` [PATCH net-next v2 1/7] net: dsa: mv888e6xxx: do not use netdev printing Vivien Didelot
2017-06-09 13:16 ` Andrew Lunn
2017-06-08 22:34 ` [PATCH net-next v2 2/7] net: dsa: mv88e6xxx: add egress mode enumeration Vivien Didelot
2017-06-08 22:34 ` [PATCH net-next v2 3/7] net: dsa: mv88e6xxx: use bridge state values Vivien Didelot
2017-06-09 13:17 ` Andrew Lunn
2017-06-08 22:34 ` [PATCH net-next v2 4/7] net: dsa: mv88e6xxx: do not prefix ops with g1 Vivien Didelot
2017-06-08 22:34 ` [PATCH net-next v2 5/7] net: dsa: mv88e6xxx: rework pause limit operation Vivien Didelot
2017-06-08 22:34 ` [PATCH net-next v2 6/7] net: dsa: mv88e6xxx: rework jumbo size operation Vivien Didelot
2017-06-08 22:34 ` [PATCH net-next v2 7/7] net: dsa: mv88e6xxx: prefix PHY macros Vivien Didelot
2017-06-09 16:11 ` 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=20170609.121120.2149178729617274766.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
all inboxes | Powered by JetHome®