From: Olof Johansson <olof@lixom.net>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: linux-tegra@vger.kernel.org, arm@kernel.org,
linux-arm-kernel@lists.infradead.org,
Jon Hunter <jonathanh@nvidia.com>
Subject: Re: [GIT PULL 1/5] firmware: tegra: Changes for v5.3-rc1
Date: Tue, 25 Jun 2019 05:42:00 -0700 [thread overview]
Message-ID: <20190625124200.toijgcugdtxheaxd@localhost> (raw)
In-Reply-To: <20190621150206.19037-1-thierry.reding@gmail.com>
On Fri, Jun 21, 2019 at 05:02:02PM +0200, Thierry Reding wrote:
> Hi ARM SoC maintainers,
>
> The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
>
> Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-5.3-firmware
>
> for you to fetch changes up to 61ed7ef952fc482ec8d4a966ed0d1e32df276c59:
>
> firmware: tegra: Early resume BPMP (2019-06-14 17:45:17 +0200)
>
> Thanks,
> Thierry
>
> ----------------------------------------------------------------
> firmware: tegra: Changes for v5.3-rc1
>
> This contains a single, simple change that resumes the BPMP driver early
> so that it is available when the various consumers want to enable their
> clocks.
Merged, thanks.
-Olof
prev parent reply other threads:[~2019-06-25 12:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 15:02 [GIT PULL 1/5] firmware: tegra: Changes for v5.3-rc1 Thierry Reding
2019-06-21 15:02 ` [GIT PULL 2/5] memory: " Thierry Reding
2019-06-25 12:42 ` Olof Johansson
2019-06-21 15:02 ` [GIT PULL 3/5] soc: " Thierry Reding
2019-06-25 12:42 ` Olof Johansson
2019-06-21 15:02 ` [GIT PULL 4/5] arm64: tegra: Device tree changes " Thierry Reding
2019-06-25 11:49 ` Olof Johansson
2019-06-21 15:02 ` [GIT PULL 5/5] arm64: tegra: Default configuration " Thierry Reding
2019-06-25 12:20 ` Olof Johansson
2019-06-25 12:42 ` Olof Johansson [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=20190625124200.toijgcugdtxheaxd@localhost \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.com \
/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).