public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: arm@kernel.org, soc@kernel.org, Jon Hunter <jonathanh@nvidia.com>,
	linux-tegra@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] arm64: tegra: Device tree fixes for v5.13-rc6
Date: Tue, 15 Jun 2021 08:24:05 -0700	[thread overview]
Message-ID: <20210615152405.GC11724@lx2k> (raw)
In-Reply-To: <20210608121457.3202430-1-thierry.reding@gmail.com>

Hi,


On Tue, Jun 08, 2021 at 02:14:57PM +0200, Thierry Reding wrote:
> Hi ARM SoC maintainers,
> 
>   Linux 5.13-rc1 (2021-05-09 14:17:44 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-5.13-arm64-dt-fixes
> 
> for you to fetch changes up to 9e79e58f330ea4860f2ced65a8a35dfb05fc03c1:
> 
>   arm64: tegra: Add PMU node for Tegra194 (2021-05-28 17:45:38 +0200)
> 
> Thanks,
> Thierry
> 
> ----------------------------------------------------------------
> arm64: tegra: Fixes for v5.13-rc6
> 
> This contains a single fix to eliminate an error message during boot
> caused by the lack of a PMU device tree node on Tegra194.

This doesn't seem to be a regression, so I'll queue it up for next release.


-Olof

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-06-15 19:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-08 12:14 [GIT PULL] arm64: tegra: Device tree fixes for v5.13-rc6 Thierry Reding
2021-06-15 15:24 ` Olof Johansson [this message]
2021-06-16  8:22   ` 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=20210615152405.GC11724@lx2k \
    --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=soc@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