From: Jiri Pirko <jiri@resnulli.us>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: dsahern@gmail.com, stephen@networkplumber.org,
netdev@vger.kernel.org, oss-drivers@netronome.com
Subject: Re: [PATCH iproute2-next v3] devlink: add info subcommand
Date: Mon, 4 Feb 2019 16:24:18 +0100 [thread overview]
Message-ID: <20190204152418.GE2118@nanopsycho> (raw)
In-Reply-To: <20190204071302.7a844b0a@cakuba.hsd1.ca.comcast.net>
Mon, Feb 04, 2019 at 04:13:02PM CET, jakub.kicinski@netronome.com wrote:
>On Mon, 4 Feb 2019 15:49:48 +0100, Jiri Pirko wrote:
>> > running:
>> > fw.bundle_id -
>>
>> Wait, what are these "-" ?
>> That looks a bit scarry.
>
>It's a test build of the FW, I wanted to show you the real output with
>all the versions reported... I can use a FW where those are just not
>reported. Do you want me to respin v4 for this?
No problem :)
Acked-by: Jiri Pirko <jiri@mellanox.com>
Thanks!
prev parent reply other threads:[~2019-02-04 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 14:43 [PATCH iproute2-next v3] devlink: add info subcommand Jakub Kicinski
2019-02-04 14:49 ` Jiri Pirko
2019-02-04 15:13 ` Jakub Kicinski
2019-02-04 15:24 ` Jiri Pirko [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=20190204152418.GE2118@nanopsycho \
--to=jiri@resnulli.us \
--cc=dsahern@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.com \
--cc=stephen@networkplumber.org \
/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).