linux-kernel - Re: [PATCH v2 2/2] dt-bindings: i2c: Update documentation for "mv78230-a0-i2c"

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:   Thu, 5 Oct 2017 18:29:53 -0500
From:   Rob Herring <robh@...nel.org>
To:     Wolfram Sang <wsa@...-dreams.de>
Cc:     Gregory CLEMENT <gregory.clement@...e-electrons.com>,
        Kalyan Kinthada <kalyan.kinthada@...iedtelesis.co.nz>,
        jason@...edaemon.net, andrew@...n.ch,
        sebastian.hesselbarth@...il.com, mark.rutland@....com,
        linux@...linux.org.uk, devicetree@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        linux-i2c@...r.kernel.org,
        Chris Packham <chris.packham@...iedtelesis.co.nz>
Subject: Re: [PATCH v2 2/2] dt-bindings: i2c: Update documentation for
 "mv78230-a0-i2c"

On Thu, Oct 05, 2017 at 01:08:20PM +0200, Wolfram Sang wrote:
> On Mon, Oct 02, 2017 at 04:23:43PM +0200, Gregory CLEMENT wrote:
> > Hi Wolfram,
> >  
> >  On ven., sept. 29 2017, Kalyan Kinthada <kalyan.kinthada@...iedtelesis.co.nz> wrote:
> > 
> > > This commit modifies the documentation for
> > > "marvell,mv78230-a0-i2c" compatible string.
> > >
> > > The "marvell,mv78230-a0-i2c" compatible string enables the workaround
> > > for an i2c repeated start timing violation, but unlike
> > > "marvell,mv78230-i2c" it disables the i2c offload support. This is
> > > applicable to a number of SoCs such as early revisions of the Armada XP
> > > and the Armada 38x.
> > >
> > > Signed-off-by: Kalyan Kinthada <kalyan.kinthada@...iedtelesis.co.nz>
> > 
> > 
> > I applied the dt fix on my mvebu/fixes branch. Do you want to apply this
> > one on your branch, or do you prefer I take it. In this case an acked-by
> > would be nice.
> 
> I'd prefer to take it. What I'd really like to see here is an ack from
> Rob because of the previous discussion of an earlier revision of this
> patch.

I'm confused how mv78230 relates to Armada XP or 38x... I don't really 
want to know either. If normal compatible string conventions were 
followed then I wouldn't have to.

Rob