From: Daniel Borkmann <daniel@iogearbox•net>
To: Jiri Pirko <jiri@resnulli•us>,
Jesper Dangaard Brouer <brouer@redhat•com>
Cc: netdev@vger•kernel.org, davem@davemloft•net, idosch@mellanox•com,
eladr@mellanox•com, yotamg@mellanox•com, ogerlitz@mellanox•com,
yishaih@mellanox•com, dledford@redhat•com, sean.hefty@intel•com,
hal.rosenstock@gmail•com, eugenia@mellanox•com,
roopa@cumulusnetworks•com, nikolay@cumulusnetworks•com,
hadarh@mellanox•com, jhs@mojatatu•com, john.fastabend@gmail•com,
jeffrey.t.kirsher@intel•com, jbenc@redhat•com
Subject: Re: [patch net-next RFC 0/6] Introduce devlink interface and first drivers to use it
Date: Wed, 03 Feb 2016 16:17:14 +0100 [thread overview]
Message-ID: <56B219FA.7080208@iogearbox.net> (raw)
In-Reply-To: <20160203133356.GA2219@nanopsycho.orion>
On 02/03/2016 02:33 PM, Jiri Pirko wrote:
> Wed, Feb 03, 2016 at 02:31:33PM CET, brouer@redhat•com wrote:
>> On Wed, 3 Feb 2016 11:47:56 +0100
>> Jiri Pirko <jiri@resnulli•us> wrote:
>>> From: Jiri Pirko <jiri@mellanox•com>
[...]
>>> It is available here:
>>> https://github.com/jpirko/devlink
>>
>> IHMO this very short command name "dl" is not an advantage. It is
>> simply too unspecific and short for a good Google search. E.g. when
>> searching for good examples for using "dl". I think "devlink" would be
>> better. If you like short commands do: alias dl="devlink"
>
> I was thinking about using "devlink". Decided to go with shortened
> version so this is in-line with "ip". But you have a point.
Btw, if you add this tool into iproute2 (which would be preferred), then
probably dl should be ok (and easier retrievable in that relation).
next prev parent reply other threads:[~2016-02-03 15:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 10:47 [patch net-next RFC 0/6] Introduce devlink interface and first drivers to use it Jiri Pirko
2016-02-03 10:47 ` [patch net-next RFC 1/6] Introduce devlink infrastructure Jiri Pirko
2016-02-11 14:31 ` Ivan Vecera
2016-02-11 16:54 ` Jiri Pirko
2016-02-03 10:47 ` [patch net-next RFC 2/6] mlxsw: Implement devlink interface Jiri Pirko
2016-02-03 10:47 ` [patch net-next RFC 3/6] mlxsw: Implement hardware messages notification using devlink Jiri Pirko
2016-02-03 10:48 ` [patch net-next RFC 4/6] mlx4: Implement devlink interface Jiri Pirko
2016-02-16 16:43 ` Or Gerlitz
2016-02-16 16:51 ` Jiri Pirko
2016-02-03 10:48 ` [patch net-next RFC 5/6] mlx4: Implement hardware messages notification using devlink Jiri Pirko
2016-02-03 10:48 ` [patch net-next RFC 6/6] mlx4: Implement port type setting via devlink interface Jiri Pirko
2016-02-03 13:31 ` [patch net-next RFC 0/6] Introduce devlink interface and first drivers to use it Jesper Dangaard Brouer
2016-02-03 13:33 ` Jiri Pirko
2016-02-03 15:17 ` Daniel Borkmann [this message]
2016-02-04 13:22 ` Hannes Frederic Sowa
2016-02-04 13:26 ` Jiri Pirko
2016-02-05 10:01 ` Hannes Frederic Sowa
2016-02-05 17:38 ` Alexei Starovoitov
2016-02-06 19:40 ` Jiri Pirko
2016-02-08 10:15 ` Hannes Frederic Sowa
2016-02-08 10:55 ` Jiri Pirko
2016-02-08 12:11 ` Hannes Frederic Sowa
2016-02-04 19:01 ` Rosen, Rami
2016-02-05 14:29 ` Jesper Dangaard Brouer
2016-02-07 20:18 ` roopa
2016-02-08 19:00 ` Doug Ledford
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=56B219FA.7080208@iogearbox.net \
--to=daniel@iogearbox$(echo .)net \
--cc=brouer@redhat$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=dledford@redhat$(echo .)com \
--cc=eladr@mellanox$(echo .)com \
--cc=eugenia@mellanox$(echo .)com \
--cc=hadarh@mellanox$(echo .)com \
--cc=hal.rosenstock@gmail$(echo .)com \
--cc=idosch@mellanox$(echo .)com \
--cc=jbenc@redhat$(echo .)com \
--cc=jeffrey.t.kirsher@intel$(echo .)com \
--cc=jhs@mojatatu$(echo .)com \
--cc=jiri@resnulli$(echo .)us \
--cc=john.fastabend@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nikolay@cumulusnetworks$(echo .)com \
--cc=ogerlitz@mellanox$(echo .)com \
--cc=roopa@cumulusnetworks$(echo .)com \
--cc=sean.hefty@intel$(echo .)com \
--cc=yishaih@mellanox$(echo .)com \
--cc=yotamg@mellanox$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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