devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Sasha Levin <sashal@kernel.org>
Cc: Jon Hunter <jonathanh@nvidia.com>,
	devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] arm64: tegra: Fix ethernet phy-mode for Jetson Xavier
Date: Thu, 7 May 2020 12:05:02 +0200	[thread overview]
Message-ID: <20200507100502.GB2890327@ulmo> (raw)
In-Reply-To: <20200506234218.4E11D2082E@mail.kernel.org>

[-- Attachment #1: Type: text/plain, Size: 2230 bytes --]

On Wed, May 06, 2020 at 11:42:17PM +0000, Sasha Levin wrote:
> Hi
> 
> [This is an automated email]
> 
> This commit has been processed because it contains a -stable tag.
> The stable tag indicates that it's relevant for the following trees: all
> 
> The bot has tested the following trees: v5.6.8, v5.4.36, v4.19.119, v4.14.177, v4.9.220, v4.4.220.
> 
> v5.6.8: Build OK!
> v5.4.36: Build OK!
> v4.19.119: Build OK!
> v4.14.177: Failed to apply! Possible dependencies:
>     5425fb15d8ee ("arm64: tegra: Add Tegra194 chip device tree")
>     b8656c673a6b ("arm64: tegra: Add device tree for the Tegra194 P2972-0000 board")
>     f69ce393ec48 ("arm64: tegra: Add GPIO controller on Tegra194")
>     f89b58ce71a9 ("arm64: tegra: Add ethernet controller on Tegra194")
> 
> v4.9.220: Failed to apply! Possible dependencies:
>     5425fb15d8ee ("arm64: tegra: Add Tegra194 chip device tree")
>     99575bceebd6 ("arm64: tegra: Add NVIDIA P2771 board support")
>     b8656c673a6b ("arm64: tegra: Add device tree for the Tegra194 P2972-0000 board")
>     f69ce393ec48 ("arm64: tegra: Add GPIO controller on Tegra194")
>     f89b58ce71a9 ("arm64: tegra: Add ethernet controller on Tegra194")
> 
> v4.4.220: Failed to apply! Possible dependencies:
>     0f279ebdf3ce ("arm64: tegra: Add NVIDIA Tegra132 Norrin support")
>     2cc85bd90337 ("arm64: tegra: Add NVIDIA P2571 board support")
>     34b4f6d0599e ("arm64: tegra: Add Tegra132 support")
>     5425fb15d8ee ("arm64: tegra: Add Tegra194 chip device tree")
>     5d17ba6e638e ("arm64: tegra: Add support for Google Pixel C")
>     63023e95bec0 ("arm64: tegra: Add NVIDIA P2371 board support")
>     99575bceebd6 ("arm64: tegra: Add NVIDIA P2771 board support")
>     b8656c673a6b ("arm64: tegra: Add device tree for the Tegra194 P2972-0000 board")
>     f69ce393ec48 ("arm64: tegra: Add GPIO controller on Tegra194")
>     f89b58ce71a9 ("arm64: tegra: Add ethernet controller on Tegra194")
> 
> 
> NOTE: The patch will not be queued to stable trees until it is upstream.
> 
> How should we proceed with this patch?

Tegra194 support was merged into v4.17, so it doesn't make backport this
to any stable kernels prior to that.

Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2020-05-07 10:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-01  7:27 [PATCH] arm64: tegra: Fix ethernet phy-mode for Jetson Xavier Jon Hunter
2020-05-05 23:12 ` Thierry Reding
2020-05-06 23:42 ` Sasha Levin
2020-05-07 10:05   ` Thierry Reding [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=20200507100502.GB2890327@ulmo \
    --to=thierry.reding@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-tegra@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@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 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).