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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YOSdgDZH5Uw9Y8yj@kroah.com>
Date:   Tue, 6 Jul 2021 20:14:24 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Wesley Cheng <wcheng@...eaurora.org>
Cc:     agross@...nel.org, bjorn.andersson@...aro.org, balbi@...nel.org,
        robh+dt@...nel.org, frowand.list@...il.com,
        linux-arm-msm@...r.kernel.org, linux-usb@...r.kernel.org,
        linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
        jackp@...eaurora.org, fntoth@...il.com
Subject: Re: [PATCH v12 6/6] dt-bindings: usb: dwc3: Update dwc3 TX fifo
 properties

On Fri, Jul 02, 2021 at 02:37:35AM -0700, Wesley Cheng wrote:
> Update the tx-fifo-resize property with a better description, while
> adding the tx-fifo-max-num, which is a new parameter allowing
> adjustments for the maximum number of packets the txfifo resizing logic
> can account for while resizing the endpoints.
> 
> Reviewed-by: Rob Herring <robh@...nel.org>
> Signed-off-by: Wesley Cheng <wcheng@...eaurora.org>
> ---
>  Documentation/devicetree/bindings/usb/snps,dwc3.yaml | 15 +++++++++++++--
>  1 file changed, 13 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/usb/snps,dwc3.yaml b/Documentation/devicetree/bindings/usb/snps,dwc3.yaml
> index 41416fb..078fb78 100644
> --- a/Documentation/devicetree/bindings/usb/snps,dwc3.yaml
> +++ b/Documentation/devicetree/bindings/usb/snps,dwc3.yaml
> @@ -289,10 +289,21 @@ properties:
>      maximum: 16
>  
>    tx-fifo-resize:
> -    description: Determines if the FIFO *has* to be reallocated
> -    deprecated: true

So this is NOT deprecated?  Are we allowed to "bring back" things people
thought were going away?

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ