From: Valentin Kleibel <valentin@vrvis.at>
To: Vinod Koul <vkoul@kernel.org>, Chukun Pan <amadeus@jmu.edu.cn>
Cc: Heiko Stuebner <heiko@sntech.de>,
Philipp Zabel <p.zabel@pengutronix.de>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Jianfeng Liu <liujianfeng1994@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org,
Jonas Karlman <jonas@kwiboo.se>
Subject: Re: [PATCH v2 0/1] phy: rockchip: naneng-combphy: compatible reset with old DT
Date: Tue, 11 Feb 2025 14:03:51 +0100 [thread overview]
Message-ID: <f64ee4ee-7e56-4423-813e-b87e023e893d@vrvis.at> (raw)
In-Reply-To: <173831716590.670164.5196739962949646746.b4-ty@kernel.org>
Hi,
>> Chukun Pan (1):
>> phy: rockchip: naneng-combphy: compatible reset with old DT
>>
>> [...]
>
> Applied, thanks!
>
> [1/1] phy: rockchip: naneng-combphy: compatible reset with old DT
> commit: bff68d44135ce6714107e2f72069a79476c8073d
Thanks for your work!
We found your patch after NVMes stopped working on a rock 3A with newer
kernels and successfully applied it to kernel 6.1.128 (currently in debian).
As the commit breaking NVMe functionality on rk3568 platforms
(fd3ac6e80497 "phy: rockchip: naneng-combphy: fix phy reset") was
already backported to 6.1.y, 6.6.y, 6.12.y it would be great to have
this fix in these releases as well.
Best regards,
Valentin
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-02-11 13:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 10:00 [PATCH v2 0/1] phy: rockchip: naneng-combphy: compatible reset with old DT Chukun Pan
2025-01-06 10:00 ` [PATCH v2 1/1] " Chukun Pan
2025-01-13 21:45 ` Jonas Karlman
2025-01-15 4:00 ` Chukun Pan
2025-01-15 8:07 ` Jonas Karlman
2025-01-30 5:57 ` Vinod Koul
2025-01-30 10:11 ` Jonas Karlman
2025-01-31 9:52 ` [PATCH v2 0/1] " Vinod Koul
2025-02-11 13:03 ` Valentin Kleibel [this message]
2025-02-18 11:45 ` Diederik de Haas
2025-02-21 7:18 ` Salvatore Bonaccorso
2025-02-21 8:57 ` Diederik de Haas
2025-02-21 9:19 ` Heiko Stübner
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=f64ee4ee-7e56-4423-813e-b87e023e893d@vrvis.at \
--to=valentin@vrvis.at \
--cc=amadeus@jmu.edu.cn \
--cc=heiko@sntech.de \
--cc=jonas@kwiboo.se \
--cc=kishon@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=liujianfeng1994@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=vkoul@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