From: Andrew Lunn <andrew@lunn.ch>
To: Tobias Waldekranz <tobias@waldekranz.com>
Cc: davem@davemloft.net, kuba@kernel.org, vivien.didelot@gmail.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: dsa: mv88e6xxx: Add helper to get a chip's max_vid
Date: Tue, 10 Nov 2020 20:23:32 +0100 [thread overview]
Message-ID: <20201110192332.GI1456319@lunn.ch> (raw)
In-Reply-To: <20201110185720.18228-1-tobias@waldekranz.com>
On Tue, Nov 10, 2020 at 07:57:20PM +0100, Tobias Waldekranz wrote:
> Most of the other chip info constants have helpers to get at them; add
> one for max_vid to keep things consistent.
>
> Suggested-by: Andrew Lunn <andrew@lunn.ch>
> Signed-off-by: Tobias Waldekranz <tobias@waldekranz.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2020-11-10 19:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 18:57 [PATCH net-next] net: dsa: mv88e6xxx: Add helper to get a chip's max_vid Tobias Waldekranz
2020-11-10 19:23 ` Andrew Lunn [this message]
2020-11-12 4:25 ` Jakub Kicinski
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=20201110192332.GI1456319@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tobias@waldekranz.com \
--cc=vivien.didelot@gmail.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).