From: Ido Schimmel <idosch@mellanox.com>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: Petr Machata <petrm@mellanox.com>, Jiri Pirko <jiri@mellanox.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
Shalom Toledo <shalomt@mellanox.com>, mlxsw <mlxsw@mellanox.com>
Subject: Re: [PATCH net-next 2/2] mlxsw: core: Add support for devlink info command
Date: Wed, 27 Mar 2019 19:44:11 +0000 [thread overview]
Message-ID: <20190327194403.GA7415@splinter> (raw)
In-Reply-To: <20190327105337.7f1f97a8@cakuba.netronome.com>
On Wed, Mar 27, 2019 at 10:53:37AM -0700, Jakub Kicinski wrote:
> On Wed, 27 Mar 2019 09:47:14 +0000, Petr Machata wrote:
> > Jakub Kicinski <jakub.kicinski@netronome.com> writes:
> >
> > > Looks good & glad to see it, but what's a PSID? ;)
> > >
> > > I found this after 5 seconds of googling:
> > >
> > > http://www.mellanox.com/page/firmware_HCA_FW_identification
> > >
> > > But it still just say "PSID" without explaining what the acronym stands
> > > for :)
> >
> > "Parameter Set ID"
> > http://www.mellanox.com/pdf/MFT/MFT_Windows_user_manual.pdf
>
> Thanks, would it be okay for you guys to spell that out, or at least
> add a description to the doc? Hopefully that can help with reuse and
> on the flip side avoiding using the same acronym for completely
> different things..
OK. We can add fw.psid to
Documentation/networking/devlink-info-versions.rst
next prev parent reply other threads:[~2019-03-27 19:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 13:46 [PATCH net-next 0/2] mlxsw: Add support for devlink info command Ido Schimmel
2019-03-26 13:46 ` [PATCH net-next 1/2] mlxsw: reg: Add MGIR register Ido Schimmel
2019-03-26 13:46 ` [PATCH net-next 2/2] mlxsw: core: Add support for devlink info command Ido Schimmel
2019-03-26 20:48 ` Jakub Kicinski
2019-03-27 9:47 ` Petr Machata
2019-03-27 17:53 ` Jakub Kicinski
2019-03-27 19:44 ` Ido Schimmel [this message]
2019-03-27 20:36 ` Jakub Kicinski
2019-03-27 11:08 ` Jiri Pirko
2019-03-27 20:58 ` [PATCH net-next 0/2] mlxsw: " David Miller
2019-03-27 21:31 ` Ido Schimmel
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=20190327194403.GA7415@splinter \
--to=idosch@mellanox.com \
--cc=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=jiri@mellanox.com \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=petrm@mellanox.com \
--cc=shalomt@mellanox.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).