From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/3] omap soc chages for v4.18 merge window
Date: Fri, 25 May 2018 14:13:36 -0700 [thread overview]
Message-ID: <20180525211336.uupk36xekpjgyf3g@localhost> (raw)
In-Reply-To: <pull-1526925630-789198@atomide.com-2>
On Mon, May 21, 2018 at 12:41:31PM -0700, Tony Lindgren wrote:
> From: "Tony Lindgren" <tony@atomide.com>
>
> The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
>
> Linux 4.17-rc1 (2018-04-15 18:24:20 -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/soc-signed
>
> for you to fetch changes up to 3bb3799cd4233b7c24622ae8c41455fb27a55c0f:
>
> Merge branch 'omap-for-v4.18/soc-fixes' into omap-for-v4.18/soc (2018-05-21 10:34:17 -0700)
Merged, thanks!
-Olof
next prev parent reply other threads:[~2018-05-25 21:13 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 [this message]
2018-05-21 19:41 ` [GIT PULL 3/3] more omap dts changes " Tony Lindgren
2018-05-25 21:14 ` Olof Johansson
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=20180525211336.uupk36xekpjgyf3g@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