From: Wolfram Sang <wsa@the-dreams.de>
To: Rob Herring <robh@kernel.org>
Cc: mark.rutland@arm.com, andrew@lunn.ch, jason@lakedaemon.net,
devicetree@vger.kernel.org, linux@armlinux.org.uk,
linux-kernel@vger.kernel.org,
Kalyan Kinthada <kalyan.kinthada@alliedtelesis.co.nz>,
Chris Packham <chris.packham@alliedtelesis.co.nz>,
linux-i2c@vger.kernel.org,
Gregory CLEMENT <gregory.clement@free-electrons.com>,
linux-arm-kernel@lists.infradead.org,
sebastian.hesselbarth@gmail.com
Subject: Re: [PATCH v2 2/2] dt-bindings: i2c: Update documentation for "mv78230-a0-i2c"
Date: Sun, 5 Nov 2017 13:54:19 +0100 [thread overview]
Message-ID: <20171105125419.p2ce2yl4nfi6lfcl@ninjato> (raw)
In-Reply-To: <20171005232953.gsxs6ecp6kopolf2@rob-hp-laptop>
[-- Attachment #1.1: Type: text/plain, Size: 1468 bytes --]
On Thu, Oct 05, 2017 at 06:29:53PM -0500, Rob Herring wrote:
> 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@alliedtelesis.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@alliedtelesis.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.
Is this a NAK or "annoyed, but don't really care"? ;)
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2017-11-05 12:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 21:36 [PATCH v2 0/2] Fix I2C repeated start timing violation on Armada-38x Kalyan Kinthada
2017-09-28 21:36 ` [PATCH v2 1/2] ARM: dts: Fix I2C repeated start issue " Kalyan Kinthada
2017-10-02 14:21 ` Gregory CLEMENT
2017-09-28 21:36 ` [PATCH v2 2/2] dt-bindings: i2c: Update documentation for "mv78230-a0-i2c" Kalyan Kinthada
[not found] ` <20170928213605.22874-3-kalyan.kinthada-6g8wRflRTwXFdCa3tKVlE6U/zSkkHjvu@public.gmane.org>
2017-10-02 14:23 ` Gregory CLEMENT
2017-10-05 11:08 ` Wolfram Sang
2017-10-05 23:29 ` Rob Herring
2017-11-05 12:54 ` Wolfram Sang [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171105125419.p2ce2yl4nfi6lfcl@ninjato \
--to=wsa@the-dreams.de \
--cc=andrew@lunn.ch \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=kalyan.kinthada@alliedtelesis.co.nz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=robh@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).