From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/2] device tree changes for omaps for v4.15 merge window
Date: Thu, 19 Oct 2017 16:04:59 -0700 [thread overview]
Message-ID: <20171019230459.GL4394@atomide.com> (raw)
In-Reply-To: <CAK8P3a15xUuFwZ16EZcefyBanXfjL8dsRUpA41a2WP=3EenFUw@mail.gmail.com>
* Arnd Bergmann <arnd@arndb.de> [171019 15:56]:
> On Fri, Oct 20, 2017 at 12:36 AM, Tony Lindgren <tony@atomide.com> wrote:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.15/dt-signed
>
> I had just figured it out myself and pulled. Thanks for the quick reply!
OK thanks!
Tony
next prev parent reply other threads:[~2017-10-19 23:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 16:39 [GIT PULL 1/2] soc changes for omaps for v4.15 merge window Tony Lindgren
2017-10-13 16:39 ` [GIT PULL 2/2] device tree " Tony Lindgren
2017-10-19 22:22 ` Arnd Bergmann
2017-10-19 22:36 ` Tony Lindgren
2017-10-19 22:54 ` Arnd Bergmann
2017-10-19 23:04 ` Tony Lindgren [this message]
2017-10-19 20:46 ` [GIT PULL 1/2] soc " Arnd Bergmann
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=20171019230459.GL4394@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).