linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: am57xx-idk: tpic2810 is on I2C bus, not SPI
Date: Tue, 28 Feb 2017 08:37:34 -0800	[thread overview]
Message-ID: <20170228163733.GT21809@atomide.com> (raw)
In-Reply-To: <504d1a9f-8c89-43b2-9a49-f130a21c50fd@ti.com>

* Andrew F. Davis <afd@ti.com> [170215 07:43]:
> On 02/15/2017 09:12 AM, Sekhar Nori wrote:
> > commit 50e95b6b854c ("ARM: dts: am57xx-idk: Add Industrial
> > output support") added the TPIC2810 device-tree node under
> > SPI bus instead of I2C1.
> > 
> 
> Well that's odd, looks like git could get confused by the lack of
> context around the node during rebases. Anyway,
> 
> Acked-by: Andrew F. Davis <afd@ti.com>

Applying into omap-for-v4.11/fixes thanks.

Tony

      reply	other threads:[~2017-02-28 16:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-15 15:12 [PATCH] ARM: dts: am57xx-idk: tpic2810 is on I2C bus, not SPI Sekhar Nori
2017-02-15 15:42 ` Andrew F. Davis
2017-02-28 16:37   ` Tony Lindgren [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=20170228163733.GT21809@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).