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]
Date:   Fri, 12 Apr 2019 09:32:48 +0100
From:   Mark Brown <>
To:     Sowjanya Komatineni <>
Cc:     "" <>,
        Jonathan Hunter <>,
        Timo Alho <>,
        "" <>,
        "" <>,
        Krishna Yarlagadda <>,
        Laxman Dewangan <>,
        "" <>,
        "" <>,
        "" <>,
        "" <>
Subject: Re: [PATCH V2 11/20] spi: expand mode support and add LSBYTE_FIRST

On Thu, Apr 11, 2019 at 07:58:33PM +0000, Sowjanya Komatineni wrote:
> > On Thu, Apr 04, 2019 at 05:14:10PM -0700, Sowjanya Komatineni wrote:

> > > Some SPI Master controllers support configuring Least significant byte 
> > > first or Most significant byte first order for transfers. Also some 
> > > SPI slave devices expect bytes to be in Least significant first order 
> > > and some devices expect Most significant first order.

> > > SPI driver declares mode and mode_bits as u16 and all bits are used.

> > > This patch changes mode and mode_bits to be u32 to allow for more mode 
> > > configurations.

> > > This patch also creates SPI_LSBYTE_FIRST mode to allow SPI clients to 
> > > choose LSByte order or MSByte order through the device tree property 
> > > spi-lsbyte-first.

> > Please submit one patch per change, each with a clear changelog, as covered in SubmittingPatches.  This makes it much easier to review things since it's easier to tell if the patch does what it was intended to do and means that if one part of the patch casues problems it won't hold up the other parts.

> I split changes on SPI code side and SPI Tegra side as separate patches.
> Do you meant to have both changes on SPI core and SPI Tegra together in a single patch?

You are expanding the size of the mode variable and adding a new mode in
the same patch.  These are two separate changes and should be in two
separate patches, as soon as you start writing "Also..." in a changelog
that should be a warning flag.

Please fix your mail client to word wrap within paragraphs at something
substantially less than 80 columns.  Doing this makes your messages much
easier to read and reply to.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)

Powered by blists - more mailing lists