linux-kernel - Re: [PATCH] devlink: fix typo in documentation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 12 Mar 2021 16:15:18 -0800
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Eva Dengler <eva.dengler@....de>, linux-doc@...r.kernel.org
Cc:     Jiri Pirko <jiri@...dia.com>, Jonathan Corbet <corbet@....net>,
        netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
        trivial@...nel.org
Subject: Re: [PATCH] devlink: fix typo in documentation

On 3/12/21 4:04 PM, Eva Dengler wrote:
> This commit fixes three spelling typos in devlink-dpipe.rst and
> devlink-port.rst.
> 
> Signed-off-by: Eva Dengler <eva.dengler@....de>

LGTM.
Acked-by: Randy Dunlap <rdunlap@...radead.org>

Thanks.

> ---
>  Documentation/networking/devlink/devlink-dpipe.rst | 2 +-
>  Documentation/networking/devlink/devlink-port.rst  | 4 ++--
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/networking/devlink/devlink-dpipe.rst b/Documentation/networking/devlink/devlink-dpipe.rst
> index 468fe1001b74..af37f250df43 100644
> --- a/Documentation/networking/devlink/devlink-dpipe.rst
> +++ b/Documentation/networking/devlink/devlink-dpipe.rst
> @@ -52,7 +52,7 @@ purposes as a standard complementary tool. The system's view from
>  ``devlink-dpipe`` should change according to the changes done by the
>  standard configuration tools.
>  
> -For example, it’s quiet common to  implement Access Control Lists (ACL)
> +For example, it’s quite common to  implement Access Control Lists (ACL)
>  using Ternary Content Addressable Memory (TCAM). The TCAM memory can be
>  divided into TCAM regions. Complex TC filters can have multiple rules with
>  different priorities and different lookup keys. On the other hand hardware
> diff --git a/Documentation/networking/devlink/devlink-port.rst b/Documentation/networking/devlink/devlink-port.rst
> index e99b41599465..ab790e7980b8 100644
> --- a/Documentation/networking/devlink/devlink-port.rst
> +++ b/Documentation/networking/devlink/devlink-port.rst
> @@ -151,7 +151,7 @@ representor netdevice.
>  -------------
>  A subfunction devlink port is created but it is not active yet. That means the
>  entities are created on devlink side, the e-switch port representor is created,
> -but the subfunction device itself it not created. A user might use e-switch port
> +but the subfunction device itself is not created. A user might use e-switch port
>  representor to do settings, putting it into bridge, adding TC rules, etc. A user
>  might as well configure the hardware address (such as MAC address) of the
>  subfunction while subfunction is inactive.
> @@ -173,7 +173,7 @@ Terms and Definitions
>     * - Term
>       - Definitions
>     * - ``PCI device``
> -     - A physical PCI device having one or more PCI bus consists of one or
> +     - A physical PCI device having one or more PCI buses consists of one or
>         more PCI controllers.
>     * - ``PCI controller``
>       -  A controller consists of potentially multiple physical functions,
> 


-- 
~Randy