public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 3/3] more omap dts changes for v4.18 merge window
Date: Fri, 25 May 2018 14:14:52 -0700	[thread overview]
Message-ID: <20180525211452.bxeda6d77x5psxaz@localhost> (raw)
In-Reply-To: <pull-1526925630-789198@atomide.com-3>

On Mon, May 21, 2018 at 12:41:32PM -0700, Tony Lindgren wrote:
> From: "Tony Lindgren" <tony@atomide.com>
> 
> The following changes since commit 8dfa75524a0e0e2b4eaf2a3dc178f6b4d8db85d9:
> 
>   ARM: dts: correct invalid I/O definition for MMC/SD card detect on T410 (2018-05-03 10:03:01 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.18/dt-part2-signed
> 
> for you to fetch changes up to 0dbf99542caf8a767ea0ac286ca8077cc5e8bd32:
> 
>   ARM: dts: am3517-evm: Add User LEDs and Pushbutton (2018-05-18 14:07:38 -0700)
> 
> ----------------------------------------------------------------
> Second set of dts changes for omap variants for v4.18 merge window
> 
> This series of changes contains fixes for already queued tps65218
> IRQ_TYPE, and fixes for omap3 and am335x use of IRQ_TYPE. There are
> also addition of oscillator clock for logicpd omap3 boards and a series
> of changes to improve support for am3517-evm board. And there is also
> a change to configure WLAN for am437x-sk-evm.

Merged, thanks!


-Olof

  reply	other threads:[~2018-05-25 21:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-21 19:41 [GIT PULL 1/3] ti-sysc array access fix for v4.18 merge window Tony Lindgren
2018-05-21 19:41 ` [GIT PULL 2/3] omap soc chages " Tony Lindgren
2018-05-25 21:13   ` Olof Johansson
2018-05-21 19:41 ` [GIT PULL 3/3] more omap dts changes " Tony Lindgren
2018-05-25 21:14   ` Olof Johansson [this message]
2018-05-25 21:12 ` [GIT PULL 1/3] ti-sysc array access fix " Olof Johansson

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=20180525211452.bxeda6d77x5psxaz@localhost \
    --to=olof@lixom.net \
    --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