From: David Miller <davem@davemloft.net>
To: idosch@idosch.org
Cc: netdev@vger.kernel.org, jacob.e.keller@intel.com,
jiri@mellanox.com, mlxsw@mellanox.com, idosch@mellanox.com
Subject: Re: [PATCH net-next] Documentation: Fix typo in devlink documentation
Date: Fri, 17 Jan 2020 04:13:32 -0800 (PST) [thread overview]
Message-ID: <20200117.041332.907915356252413057.davem@davemloft.net> (raw)
In-Reply-To: <20200116175944.1958052-1-idosch@idosch.org>
From: Ido Schimmel <idosch@idosch.org>
Date: Thu, 16 Jan 2020 19:59:44 +0200
> From: Ido Schimmel <idosch@mellanox.com>
>
> The driver is named "mlxsw", not "mlx5".
>
> Fixes: d4255d75856f ("devlink: document info versions for each driver")
> Signed-off-by: Ido Schimmel <idosch@mellanox.com>
Applied, thanks.
prev parent reply other threads:[~2020-01-19 11:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 17:59 [PATCH net-next] Documentation: Fix typo in devlink documentation Ido Schimmel
2020-01-16 19:09 ` Jacob Keller
2020-01-17 12:13 ` David Miller [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=20200117.041332.907915356252413057.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=idosch@idosch.org \
--cc=idosch@mellanox.com \
--cc=jacob.e.keller@intel.com \
--cc=jiri@mellanox.com \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.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).