From: Steen Hegelund <steen.hegelund@microchip.com>
To: Kishon Vijay Abraham I <kishon@ti.com>, Vinod Koul <vkoul@kernel.org>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Lars Povlsen <lars.povlsen@microchip.com>,
Bjarni Jonasson <bjarni.jonasson@microchip.com>,
Microchip UNG Driver List <UNGLinuxDriver@microchip.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH v12 2/4] phy: Add ethernet serdes configuration option
Date: Fri, 22 Jan 2021 16:07:16 +0100 [thread overview]
Message-ID: <2c7474cf57964935cebd75083229cdee14064a79.camel@microchip.com> (raw)
In-Reply-To: <92a943cc-b332-4ac6-42a8-bb3cdae13bc0@ti.com>
Hi Kishon and Vinod,
On Fri, 2021-01-15 at 21:22 +0530, Kishon Vijay Abraham I wrote:
> >
> >
I was just wanted to know if there are any outstanding items that you
would like me to handle, or you think that the driver is acceptable as
it is now?
BR
Steen
next prev parent reply other threads:[~2021-01-22 15:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 9:19 [PATCH v12 0/4] Adding the Sparx5 Serdes driver Steen Hegelund
2021-01-07 9:19 ` [PATCH v12 1/4] dt-bindings: phy: Add sparx5-serdes bindings Steen Hegelund
2021-01-14 11:02 ` Alexandre Belloni
2021-01-07 9:19 ` [PATCH v12 2/4] phy: Add ethernet serdes configuration option Steen Hegelund
2021-01-14 11:02 ` Alexandre Belloni
2021-01-15 8:44 ` Kishon Vijay Abraham I
2021-01-15 9:08 ` Steen Hegelund
2021-01-15 15:52 ` Kishon Vijay Abraham I
2021-01-15 16:14 ` Steen Hegelund
2021-01-27 12:34 ` Kishon Vijay Abraham I
2021-01-27 14:45 ` Steen Hegelund
2021-01-22 15:07 ` Steen Hegelund [this message]
2021-01-07 9:19 ` [PATCH v12 3/4] phy: Add Sparx5 ethernet serdes PHY driver Steen Hegelund
2021-01-14 11:03 ` Alexandre Belloni
2021-01-07 9:19 ` [PATCH v12 4/4] arm64: dts: sparx5: Add Sparx5 serdes driver node Steen Hegelund
2021-01-14 11:03 ` Alexandre Belloni
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=2c7474cf57964935cebd75083229cdee14064a79.camel@microchip.com \
--to=steen.hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=bjarni.jonasson@microchip.com \
--cc=kishon@ti.com \
--cc=lars.povlsen@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).