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  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:   Mon, 3 Apr 2017 10:24:03 -0500
From:   Rob Herring <>
To:     Christopher Bostic <>
Subject: Re: [PATCH v4 12/23] drivers/fsi: Add documentation for GPIO bindings

On Wed, Mar 29, 2017 at 12:43:29PM -0500, Christopher Bostic wrote:
> From: Chris Bostic <>
> Add fsi master gpio device tree binding documentation
> Signed-off-by: Chris Bostic <>
> Signed-off-by: Joel Stanley <>
> ---
>  .../devicetree/bindings/fsi/fsi-master-gpio.txt    | 24 ++++++++++++++++++++++
>  1 file changed, 24 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/fsi/fsi-master-gpio.txt

Acked-by: Rob Herring <> 

But what happened to the bus description? There's never a need to 
describe slave devices (even discoverable buses like USB and PCI still 
need them sometimes)? As it stands now, I have no idea what FSI is from 
reading bindings/fsi/*.


Powered by blists - more mailing lists