All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: arm@kernel.org
Cc: linux-tegra@vger.kernel.org,
	Thierry Reding <thierry.reding@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	Jon Hunter <jonathanh@nvidia.com>
Subject: NVIDIA Tegra changes for v4.19-rc1
Date: Thu, 12 Jul 2018 17:41:23 +0200	[thread overview]
Message-ID: <20180712154128.22705-1-thierry.reding@gmail.com> (raw)

Hi ARM SoC maintainers,

Here's the set of Tegra-related pull requests for v4.19-rc1. I'm sending
these a week earlier than usual because I will be on vacation for the
next two weeks. During my absence, Jon Hunter will be taking the helm.
Unfortunately he doesn't have access to the kernel.org repository, so if
anything comes up he may have to send patches to you directly. That said
I don't expect any issues with these pull requests. They've all soaked
in linux-next for a little while and I've done my regular sanity builds
and didn't see any issues.

In the unlikely case that everything falls apart, I'll be back shortly
after v4.18-rc7, which should give us a little time to clean things up
before the merge window.

Thanks,
Thierry

WARNING: multiple messages have this Message-ID (diff)
From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: NVIDIA Tegra changes for v4.19-rc1
Date: Thu, 12 Jul 2018 17:41:23 +0200	[thread overview]
Message-ID: <20180712154128.22705-1-thierry.reding@gmail.com> (raw)

Hi ARM SoC maintainers,

Here's the set of Tegra-related pull requests for v4.19-rc1. I'm sending
these a week earlier than usual because I will be on vacation for the
next two weeks. During my absence, Jon Hunter will be taking the helm.
Unfortunately he doesn't have access to the kernel.org repository, so if
anything comes up he may have to send patches to you directly. That said
I don't expect any issues with these pull requests. They've all soaked
in linux-next for a little while and I've done my regular sanity builds
and didn't see any issues.

In the unlikely case that everything falls apart, I'll be back shortly
after v4.18-rc7, which should give us a little time to clean things up
before the merge window.

Thanks,
Thierry

             reply	other threads:[~2018-07-12 15:41 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-12 15:41 Thierry Reding [this message]
2018-07-12 15:41 ` NVIDIA Tegra changes for v4.19-rc1 Thierry Reding
2018-07-12 15:41 ` [GIT PULL 1/5] dt-bindings: tegra: Changes " Thierry Reding
2018-07-12 15:41   ` Thierry Reding
2018-07-14 21:20   ` Olof Johansson
2018-07-14 21:20     ` Olof Johansson
2018-07-12 15:41 ` [GIT PULL 2/5] memory: " Thierry Reding
2018-07-12 15:41   ` Thierry Reding
2018-07-14 21:40   ` Olof Johansson
2018-07-14 21:40     ` Olof Johansson
2018-07-12 15:41 ` [GIT PULL 3/5] firmware: " Thierry Reding
2018-07-12 15:41   ` Thierry Reding
2018-07-14 21:45   ` Olof Johansson
2018-07-14 21:45     ` Olof Johansson
2018-07-12 15:41 ` [GIT PULL 4/5] ARM: tegra: Device tree changes " Thierry Reding
2018-07-12 15:41   ` Thierry Reding
2018-07-14 21:21   ` Olof Johansson
2018-07-14 21:21     ` Olof Johansson
2018-07-12 15:41 ` [GIT PULL 5/5] arm64: " Thierry Reding
2018-07-12 15:41   ` Thierry Reding
2018-07-14 21:22   ` Olof Johansson
2018-07-14 21:22     ` Olof Johansson
2018-08-03 10:43     ` Thierry Reding
2018-08-03 10:43       ` Thierry Reding
2018-08-03 11:26       ` Anthony Eden
2018-08-03 11:26         ` Anthony Eden
2018-08-09 10:21         ` Thierry Reding
2018-08-09 10:21           ` Thierry Reding
2018-08-09 10:34           ` Mikko Perttunen
2018-08-09 10:34             ` Mikko Perttunen
2018-08-09 14:07             ` Thierry Reding
2018-08-09 14:07               ` Thierry Reding
2018-11-03 20:08               ` Anthony Eden
2018-11-03 20:08                 ` Anthony Eden
2018-07-12 16:01 ` NVIDIA Tegra " Olof Johansson
2018-07-12 16:01   ` Olof Johansson
2018-07-13 14:09   ` Jon Hunter
2018-07-13 14:09     ` Jon Hunter

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=20180712154128.22705-1-thierry.reding@gmail.com \
    --to=thierry.reding@gmail.com \
    --cc=arm@kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-tegra@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.