From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/2] ARM: tegra: Core code changes for v4.1-rc1
Date: Thu, 2 Apr 2015 19:19:22 +0200 [thread overview]
Message-ID: <20150402171920.GA2677@ulmo.nvidia.com> (raw)
In-Reply-To: <1427710333-13472-1-git-send-email-thierry.reding@gmail.com>
On Mon, Mar 30, 2015 at 12:12:12PM +0200, Thierry Reding wrote:
> Hi ARM SoC maintainers,
>
> The following changes since commit c517d838eb7d07bbe9507871fab3931deccff539:
>
> Linux 4.0-rc1 (2015-02-22 18:21:14 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-4.1-soc
>
> for you to fetch changes up to 5a240eff95e89af9648551a7686b0e5a7d0231ab:
>
> memory: tegra: Add SWGROUP names (2015-03-30 11:47:40 +0200)
Please don't merge this just yet. Mark Brown reported that this causes
build failures in linux-next and I'm working on a couple of patches to
fix this.
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150402/f49a1d63/attachment.sig>
next prev parent reply other threads:[~2015-04-02 17:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 10:12 [GIT PULL 1/2] ARM: tegra: Core code changes for v4.1-rc1 Thierry Reding
2015-03-30 10:12 ` [GIT PULL 2/2] ARM: tegra: Device tree " Thierry Reding
2015-04-03 20:51 ` Olof Johansson
2015-04-02 17:19 ` Thierry Reding [this message]
2015-04-10 14:22 ` [GIT PULL v2 1/2] ARM: tegra: Core code " Thierry Reding
2015-04-11 1:52 ` Michael Turquette
2015-04-13 23:09 ` Arnd Bergmann
2015-04-14 7:06 ` Thierry Reding
2015-04-14 8:30 ` Arnd Bergmann
2015-04-14 11:14 ` Thierry Reding
2015-04-14 11:19 ` 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=20150402171920.GA2677@ulmo.nvidia.com \
--to=thierry.reding@gmail.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).