From: Roger Quadros <rogerq@kernel.org>
To: "Marcin Wierzbicki" <mawierzb@cisco.com>,
"Vinod Koul" <vkoul@kernel.org>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Swapnil Jakhade" <sjakhade@cadence.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: xe-linux-external@cisco.com, danielwa@cisco.com,
olicht@cisco.com, Bartosz Wawrzyniak <bwawrzyn@cisco.com>
Subject: Re: [PATCH v3] phy: cadence: Sierra: Add single link SGMII register configuration
Date: Tue, 23 May 2023 15:15:39 +0300 [thread overview]
Message-ID: <a04a6afa-6daf-ca50-9a99-d52764def948@kernel.org> (raw)
In-Reply-To: <20230522172415.1668975-1-mawierzb@cisco.com>
On 22/05/2023 20:24, Marcin Wierzbicki wrote:
> Add single link SGMII register configuration for no SSC for
> cdns,sierra-phy-t0 compatibility string.
> The configuration is based on Sierra Programmer's Guide and
> validated in Cisco CrayAR SoC.
>
> Co-developed-by: Bartosz Wawrzyniak <bwawrzyn@cisco.com>
> Signed-off-by: Bartosz Wawrzyniak <bwawrzyn@cisco.com>
> Signed-off-by: Marcin Wierzbicki <mawierzb@cisco.com>
> ---
> v3> - all reported comments were addressed
:)
You should summarize what changes were done.
> - v2: https://lore.kernel.org/lkml/20230508160142.2489365-1-mawierzb@cisco.com/T/#u
>
> v2
> - rebased version on top of commit 0cfa43ab46b5 ("phy: cadence: Sierra: Add PCIe + SGMII PHY multilink configuration")
> - v1: https://lore.kernel.org/lkml/20230419093008.195094-1-mawierzb@cisco.com/T/
>
> Regards,
> Marcin
Reviewed-by: Roger Quadros <rogerq@kernel.org>
--
cheers,
-roger
next prev parent reply other threads:[~2023-05-23 12:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 17:24 [PATCH v3] phy: cadence: Sierra: Add single link SGMII register configuration Marcin Wierzbicki
2023-05-23 12:15 ` Roger Quadros [this message]
2023-05-23 12:58 ` Marcin Wierzbicki
2023-06-21 17:39 ` Vinod Koul
2023-06-21 17:51 ` Vinod Koul
2023-07-11 11:25 ` Vinod Koul
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=a04a6afa-6daf-ca50-9a99-d52764def948@kernel.org \
--to=rogerq@kernel.org \
--cc=bwawrzyn@cisco.com \
--cc=danielwa@cisco.com \
--cc=kishon@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=mawierzb@cisco.com \
--cc=olicht@cisco.com \
--cc=sjakhade@cadence.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=vkoul@kernel.org \
--cc=xe-linux-external@cisco.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox