From: Andrew Lunn <andrew@lunn.ch>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"vivien.didelot@gmail.com" <vivien.didelot@gmail.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"cphealy@gmail.com" <cphealy@gmail.com>,
"jiri@nvidia.com" <jiri@nvidia.com>
Subject: Re: [PATCH net-next 0/2] Devlink regions for SJA1105 DSA driver
Date: Mon, 21 Sep 2020 21:42:10 +0200 [thread overview]
Message-ID: <20200921194210.GH3717417@lunn.ch> (raw)
In-Reply-To: <20200921191008.urnhrb4iuk5hmzer@skbuf>
On Mon, Sep 21, 2020 at 07:10:09PM +0000, Vladimir Oltean wrote:
> On Mon, Sep 21, 2020 at 09:03:27PM +0200, Andrew Lunn wrote:
> > Vladimir, could you implement the devlink DEVLINK_CMD_INFO_GET request
> > so we know what sort of device is exporting the regions, and hence
> > which pretty printers are relevant.
>
> Should I do that in this series or separately?
Up to you. I added it as part of the regions patchset. I need to know
which particular device it is in order to decode the registers
correctly.
Andrew
next prev parent reply other threads:[~2020-09-21 19:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 16:27 [PATCH net-next 0/2] Devlink regions for SJA1105 DSA driver Vladimir Oltean
2020-09-21 16:27 ` [PATCH net-next 1/2] net: dsa: sja1105: move devlink param code to sja1105_devlink.c Vladimir Oltean
2020-09-21 16:27 ` [PATCH net-next 2/2] net: dsa: sja1105: expose static config as devlink region Vladimir Oltean
2020-09-23 0:37 ` David Miller
2020-09-21 17:12 ` [PATCH net-next 0/2] Devlink regions for SJA1105 DSA driver Andrew Lunn
2020-09-21 18:12 ` Vladimir Oltean
2020-09-21 18:44 ` Florian Fainelli
2020-09-21 19:03 ` Andrew Lunn
2020-09-21 19:10 ` Vladimir Oltean
2020-09-21 19:42 ` Andrew Lunn [this message]
2020-09-21 19:47 ` Vladimir Oltean
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=20200921194210.GH3717417@lunn.ch \
--to=andrew@lunn.ch \
--cc=cphealy@gmail.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@gmail.com \
--cc=vladimir.oltean@nxp.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).