From: Vinod Koul <vkoul@kernel.org>
To: Sean Anderson <sean.anderson@seco.com>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
Ioana Ciornei <ioana.ciornei@nxp.com>,
linux-arm-kernel@lists.infradead.org,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Madalin Bucur <madalin.bucur@nxp.com>,
Camelia Alexandra Groza <camelia.groza@nxp.com>,
linuxppc-dev@lists.ozlabs.org, Rob Herring <robh+dt@kernel.org>,
Jonathan Corbet <corbet@lwn.net>, Li Yang <leoyang.li@nxp.com>,
Michael Turquette <mturquette@baylibre.com>,
Shawn Guo <shawnguo@kernel.org>, Stephen Boyd <sboyd@kernel.org>,
linux-clk@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v5 0/8] phy: Add support for Lynx 10G SerDes
Date: Tue, 13 Sep 2022 23:14:22 +0530 [thread overview]
Message-ID: <YyDBdn+IHqConzIW@matsya> (raw)
In-Reply-To: <de50858e-0056-fd72-2b67-27bf597b3366@seco.com>
On 09-09-22, 11:05, Sean Anderson wrote:
>
> I noticed in patchwork [1] that this entire series is marked as "Changes
> Requested," despite having received only automated feedback on one patch
> in the series. I am concerned about this because last time this occurred
> [2], the series received no feedback for a month. I suspect this is
> because series marked "Changes Requested" are hidden in patchwork by
> default. Can you change the status of this series back to new? Or should
> I just resend again?
Yes please, update with ack collected any feedback addressed would be
right...
> [1] https://patchwork.kernel.org/project/linux-phy/list/?series=673741&state=*
> [2] https://patchwork.kernel.org/project/linux-phy/list/?series=665484&state=*
--
~Vinod
prev parent reply other threads:[~2022-09-13 18:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 21:37 [PATCH v5 0/8] phy: Add support for Lynx 10G SerDes Sean Anderson
2022-09-02 21:37 ` [PATCH v5 1/8] dt-bindings: phy: Add 2500BASE-X and 10GBASE-R Sean Anderson
2022-09-12 19:49 ` Rob Herring
2022-09-02 21:37 ` [PATCH v5 2/8] dt-bindings: phy: Add Lynx 10G phy binding Sean Anderson
2022-09-12 19:46 ` Rob Herring
2022-09-02 21:37 ` [PATCH v5 3/8] dt-bindings: clock: Add ids for Lynx 10g PLLs Sean Anderson
2022-09-12 19:50 ` Rob Herring
2022-09-02 21:37 ` [PATCH v5 4/8] phy: fsl: Add Lynx 10G SerDes driver Sean Anderson
2022-09-03 15:23 ` kernel test robot
2022-09-06 16:33 ` Sean Anderson
2022-09-02 21:37 ` [PATCH v5 5/8] arm64: dts: ls1046a: Add serdes bindings Sean Anderson
2022-09-02 21:37 ` [PATCH v5 6/8] arm64: dts: ls1088a: " Sean Anderson
2022-09-02 21:37 ` [PATCH v5 7/8] arm64: dts: ls1046ardb: " Sean Anderson
2022-09-02 21:37 ` [PATCH v5 8/8] [WIP] arm64: dts: ls1088ardb: " Sean Anderson
2022-09-09 15:05 ` [PATCH v5 0/8] phy: Add support for Lynx 10G SerDes Sean Anderson
2022-09-13 17:44 ` Vinod Koul [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=YyDBdn+IHqConzIW@matsya \
--to=vkoul@kernel.org \
--cc=camelia.groza@nxp.com \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=ioana.ciornei@nxp.com \
--cc=kishon@ti.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madalin.bucur@nxp.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=sean.anderson@seco.com \
--cc=shawnguo@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).