linux-kernel - Re: [PATCH] Documentation: connector: Update the description of sink-vdos

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] [day] [month] [year] [list]

Message-ID: <20210212152114.GC57042@roeck-us.net>
Date:   Fri, 12 Feb 2021 07:21:14 -0800
From:   Guenter Roeck <linux@...ck-us.net>
To:     Kyle Tso <kyletso@...gle.com>
Cc:     robh+dt@...nel.org, heikki.krogerus@...ux.intel.com,
        gregkh@...uxfoundation.org, badhri@...gle.com,
        linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
        devicetree@...r.kernel.org
Subject: Re: [PATCH] Documentation: connector: Update the description of
 sink-vdos

On Fri, Feb 12, 2021 at 03:37:43PM +0800, Kyle Tso wrote:
> Remove the acronym "VDM" and replace it with the full name "Vendor
> Defined Message".
> 
> Signed-off-by: Kyle Tso <kyletso@...gle.com>

Reviewed-by: Guenter Roeck <linux@...ck-us.net>

> ---
>  .../devicetree/bindings/connector/usb-connector.yaml       | 7 ++++---
>  1 file changed, 4 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/connector/usb-connector.yaml b/Documentation/devicetree/bindings/connector/usb-connector.yaml
> index d385026944ec..ce11b2027199 100644
> --- a/Documentation/devicetree/bindings/connector/usb-connector.yaml
> +++ b/Documentation/devicetree/bindings/connector/usb-connector.yaml
> @@ -138,9 +138,10 @@ properties:
>      $ref: /schemas/types.yaml#/definitions/uint32-array
>  
>    sink-vdos:
> -    description: An array of u32 with each entry (VDM Objects) providing additional information
> -      corresponding to the product, the detailed bit definitions and the order of each VDO can be
> -      found in "USB Power Delivery Specification Revision 3.0, Version 2.0 + ECNs 2020-12-10"
> +    description: An array of u32 with each entry, a Vendor Defined Message Object (VDO),
> +      providing additional information corresponding to the product, the detailed bit
> +      definitions and the order of each VDO can be found in
> +      "USB Power Delivery Specification Revision 3.0, Version 2.0 + ECNs 2020-12-10"
>        chapter 6.4.4.3.1 Discover Identity. User can specify the VDO array via
>        VDO_IDH/_CERT/_PRODUCT/_UFP/_DFP/_PCABLE/_ACABLE(1/2)/_VPD() defined in
>        dt-bindings/usb/pd.h.
> -- 
> 2.30.0.478.g8a0d178c01-goog
>