From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: stable@vger.kernel.org, linux-tegra <linux-tegra@vger.kernel.org>,
Thierry Reding <thierry.reding@gmail.com>
Subject: Re: stable request: 5.4.y: arm64: tegra: Fix 'active-low' warning for Jetson
Date: Fri, 6 Dec 2019 13:53:34 +0100 [thread overview]
Message-ID: <20191206125334.GA1361962@kroah.com> (raw)
In-Reply-To: <16724779-0514-ca92-58b2-95f4e244c6f7@nvidia.com>
On Fri, Dec 06, 2019 at 10:55:17AM +0000, Jon Hunter wrote:
> Hi Greg,
>
> Please can you include the following device-tree fixes for 5.4.y that
> are triggering some warnings on a couple of our Jetson platforms. This
> is currently causing one of our kernel warnings tests to fail. Both of
> these have now been merged into the mainline for v5.5-rc1.
>
> commit d440538e5f219900a9fc9d96fd10727b4d2b3c48
> Author: Jon Hunter <jonathanh@nvidia.com>
> Date: Wed Sep 25 15:12:28 2019 +0100
>
> arm64: tegra: Fix 'active-low' warning for Jetson Xavier regulator
>
> commit 1e5e929c009559bd7e898ac8e17a5d01037cb057
> Author: Jon Hunter <jonathanh@nvidia.com>
> Date: Wed Sep 25 15:12:29 2019 +0100
>
> arm64: tegra: Fix 'active-low' warning for Jetson TX1 regulator
>
> Thanks
> Jon
Now queued up, thanks.
greg k-h
next prev parent reply other threads:[~2019-12-06 12:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 10:55 stable request: 5.4.y: arm64: tegra: Fix 'active-low' warning for Jetson Jon Hunter
2019-12-06 10:55 ` Jon Hunter
2019-12-06 11:04 ` Jon Hunter
2019-12-06 11:04 ` Jon Hunter
2019-12-06 12:23 ` Greg Kroah-Hartman
2019-12-06 12:58 ` Jon Hunter
2019-12-06 12:58 ` Jon Hunter
2019-12-06 12:53 ` Greg Kroah-Hartman [this message]
2019-12-06 13:16 ` Jon Hunter
2019-12-06 13:16 ` Jon Hunter
2019-12-06 13:33 ` Greg Kroah-Hartman
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=20191206125334.GA1361962@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=stable@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 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.