public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, arm@kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 1/2] device tree changes for omaps for v5.2
Date: Sun, 28 Apr 2019 12:32:49 -0700	[thread overview]
Message-ID: <20190428193249.uufhjnvkuzxhh6xp@localhost> (raw)
In-Reply-To: <pull-1555343712-332506@atomide.com>

On Mon, Apr 15, 2019 at 10:00:53AM -0700, Tony Lindgren wrote:
> From: "Tony Lindgren" <tony@atomide.com>
> 
> The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
> 
>   Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v5.2/dt-signed
> 
> for you to fetch changes up to bcbb63b80284af0061ac44fe944d31a8482d2b8a:
> 
>   ARM: dts: dra7: Separate AM57 dtsi files (2019-04-12 09:57:07 -0700)
> 
> ----------------------------------------------------------------
> Devicetree changes for omap variants
> 
> This series of changes configures dra7 pcie x2 lane mode, configures
> am43xx-epos-evm regulators and keypad wakeup source, and uses standard
> reset-gpios instead of gpio-reset for n810.
> 
> We also need to split dra7 dtsi files for properly supporting dra76x
> and am576 as some of the devices are different such as usb and pruss.

Merged, thanks!


-Olof

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      parent reply	other threads:[~2019-04-28 20:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-15 17:00 [GIT PULL 1/2] device tree changes for omaps for v5.2 Tony Lindgren
2019-04-15 17:00 ` [GIT PULL 2/2] dts changes for ti-sysc driver " Tony Lindgren
2019-04-28 19:34   ` Olof Johansson
2019-04-28 19:32 ` Olof Johansson [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=20190428193249.uufhjnvkuzxhh6xp@localhost \
    --to=olof@lixom.net \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.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