From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/4] ARM: tegra: Core SoC changes for v4.8-rc1
Date: Thu, 14 Jul 2016 15:38:04 +0200 [thread overview]
Message-ID: <7084807.7TOvWKuOqd@wuerfel> (raw)
In-Reply-To: <20160711152512.11731-1-thierry.reding@gmail.com>
On Monday, July 11, 2016 5:25:09 PM CEST Thierry Reding wrote:
> ARM: tegra: Core SoC changes for v4.8-rc1
>
> Some cleanups to eliminate sparse warnings and a section mismatch.
>
Pulled into next/cleanup, thanks!
Arnd
prev parent reply other threads:[~2016-07-14 13:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 15:25 [GIT PULL 1/4] ARM: tegra: Core SoC changes for v4.8-rc1 Thierry Reding
2016-07-11 15:25 ` [GIT PULL 2/4] ARM: tegra: Device tree " Thierry Reding
2016-07-14 13:41 ` Arnd Bergmann
2016-07-11 15:25 ` [GIT PULL 3/4] arm64: " Thierry Reding
2016-07-11 15:25 ` [GIT PULL 4/4] arm64: tegra: Default configuration updates " Thierry Reding
2016-07-14 13:55 ` Arnd Bergmann
2016-07-14 13:38 ` Arnd Bergmann [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=7084807.7TOvWKuOqd@wuerfel \
--to=arnd@arndb.de \
--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).