public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>,
	Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH for 5.4 - 6.1 1/3] ARM: dts: am335x-bone-common: Add GPIO PHY reset on revision C3 board
Date: Sat, 21 Jun 2025 04:50:58 -0400	[thread overview]
Message-ID: <20250621042012-6f3bb7a44693cded@stable.kernel.org> (raw)
In-Reply-To: <1750381987-6825-1-git-send-email-nobuhiro1.iwamatsu@toshiba.co.jp>

[ Sasha's backport helper bot ]

Hi,

✅ All tests passed successfully. No issues detected.
No action required from the submitter.

The upstream commit SHA1 provided is correct: 623cef652768860bd5f205fb7b741be278585fba

WARNING: Author mismatch between patch and upstream commit:
Backport author: Nobuhiro Iwamatsu<nobuhiro1.iwamatsu@toshiba.co.jp>
Commit author: Shengyu Qu<wiagn233@outlook.com>

Status in newer kernel trees:
6.15.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (exact SHA1)
6.1.y | Not found
5.15.y | Not found
5.10.y | Not found

Note: The patch differs from the upstream commit:
---
1:  623cef6527688 ! 1:  01338e4054b9b ARM: dts: am335x-bone-common: Add GPIO PHY reset on revision C3 board
    @@ Metadata
      ## Commit message ##
         ARM: dts: am335x-bone-common: Add GPIO PHY reset on revision C3 board
     
    +    commit 623cef652768860bd5f205fb7b741be278585fba upstream.
    +
         This patch adds ethernet PHY reset GPIO config for Beaglebone Black
         series boards with revision C3. This fixes a random phy startup failure
         bug discussed at [1]. The GPIO pin used for reset is not used on older
    @@ Commit message
         Signed-off-by: Shengyu Qu <wiagn233@outlook.com>
         Message-ID: <TY3P286MB26113797A3B2EC7E0348BBB2980FA@TY3P286MB2611.JPNP286.PROD.OUTLOOK.COM>
         Signed-off-by: Tony Lindgren <tony@atomide.com>
    +    Signed-off-by: Nobuhiro Iwamatsu (CIP) <nobuhiro1.iwamatsu@toshiba.co.jp>
     
    - ## arch/arm/boot/dts/ti/omap/am335x-bone-common.dtsi ##
    + ## arch/arm/boot/dts/am335x-bone-common.dtsi ##
     @@
      			/* MDIO */
      			AM33XX_PADCONF(AM335X_PIN_MDIO, PIN_INPUT_PULLUP | SLEWCTRL_FAST, MUX_MODE0)
---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.1.y        |  Success    |  Success   |

      parent reply	other threads:[~2025-06-21  8:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-20  1:13 [PATCH for 5.4 - 6.1 1/3] ARM: dts: am335x-bone-common: Add GPIO PHY reset on revision C3 board Nobuhiro Iwamatsu
2025-06-20  1:13 ` [PATCH for 5.4 - 6.1 2/3] ARM: dts: am335x-bone-common: Increase MDIO reset deassert time Nobuhiro Iwamatsu
2025-06-21  8:52   ` Sasha Levin
2025-06-20  1:13 ` [PATCH for 5.4 - 6.1 3/3] ARM: dts: am335x-bone-common: Increase MDIO reset deassert delay to 50ms Nobuhiro Iwamatsu
2025-06-21  8:52   ` Sasha Levin
2025-06-21  8:50 ` Sasha Levin [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=20250621042012-6f3bb7a44693cded@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=nobuhiro1.iwamatsu@toshiba.co.jp \
    --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