From: Jacob Keller <jacob.e.keller@intel.com>
To: netdev@vger.kernel.org
Cc: Michal Kalderon <mkalderon@marvell.com>
Subject: Re: [PATCH] devlink: fix typos in qed documentation
Date: Tue, 14 Jan 2020 12:10:50 -0800 [thread overview]
Message-ID: <a965462d-1451-34b0-4be0-902d0c096cbf@intel.com> (raw)
In-Reply-To: <20200114200918.2753721-1-jacob.e.keller@intel.com>
On 1/14/2020 12:09 PM, Jacob Keller wrote:
> Review of the recently added documentation file for the qed driver
> noticed a couple of typos. Fix them now.
>
> Noticed-by: Michal Kalderon <mkalderon@marvell.com>
> Fixes: 0f261c3ca09e ("devlink: add a driver-specific file for the qed driver")
> Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
This fixes some typos in the recently merged devlink documentation
refactor patches on net-next.
Thanks,
Jake
> ---
> Documentation/networking/devlink/qed.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/networking/devlink/qed.rst b/Documentation/networking/devlink/qed.rst
> index e7e17acf1eca..805c6f63621a 100644
> --- a/Documentation/networking/devlink/qed.rst
> +++ b/Documentation/networking/devlink/qed.rst
> @@ -22,5 +22,5 @@ The ``qed`` driver implements the following driver-specific parameters.
> * - ``iwarp_cmt``
> - Boolean
> - runtime
> - - Enable iWARP functionality for 100g devices. Notee that this impacts
> - L2 performance, and is therefor not enabled by default.
> + - Enable iWARP functionality for 100g devices. Note that this impacts
> + L2 performance, and is therefore not enabled by default.
>
next prev parent reply other threads:[~2020-01-14 20:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 20:09 [PATCH] devlink: fix typos in qed documentation Jacob Keller
2020-01-14 20:10 ` Jacob Keller [this message]
2020-01-15 22:14 ` David Miller
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=a965462d-1451-34b0-4be0-902d0c096cbf@intel.com \
--to=jacob.e.keller@intel.com \
--cc=mkalderon@marvell.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).