From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: <kishon@ti.com>, <robh+dt@kernel.org>, <andrew@lunn.ch>,
<alexandre.belloni@bootlin.com>, <kuba@kernel.org>,
<linux-phy@lists.infradead.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH resend v4 0/3] phy: Add driver for lan966x Serdes driver
Date: Tue, 16 Nov 2021 11:56:01 +0100 [thread overview]
Message-ID: <20211116105601.fauvfv2wzlmcf6jc@soft-dev3-1.localhost> (raw)
In-Reply-To: <YZOLyQPsgoOYJZch@matsya>
The 11/16/2021 16:15, Vinod Koul wrote:
>
> On 16-11-21, 11:21, Horatiu Vultur wrote:
> > The 11/16/2021 11:08, Horatiu Vultur wrote:
> >
> > Hi Kison, Vinod,
> >
> > Can you let me know if you have more comments to this patch series?
> > Otherwise can you ack on it? Because I would like to have the patches
> > merged via netdev if that is OK for you.
>
> Any reason for merge thru netdev, there is no dependency and now with
> merge window closed, I can pick this up..
Because I would like to send some patches for the lan966x network driver.
And these network patches depend on the serdes driver.
>
> --
> ~Vinod
--
/Horatiu
next prev parent reply other threads:[~2021-11-16 10:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 10:08 [PATCH resend v4 0/3] phy: Add driver for lan966x Serdes driver Horatiu Vultur
2021-11-16 10:08 ` [PATCH resend v4 1/3] dt-bindings: phy: Add lan966x-serdes binding Horatiu Vultur
2021-11-30 14:02 ` Geert Uytterhoeven
2021-11-30 16:11 ` Horatiu Vultur
2021-11-16 10:08 ` [PATCH resend v4 2/3] dt-bindings: phy: Add constants for lan966x serdes Horatiu Vultur
2021-11-16 10:08 ` [PATCH resend v4 3/3] phy: Add lan966x ethernet serdes PHY driver Horatiu Vultur
2021-11-16 10:21 ` [PATCH resend v4 0/3] phy: Add driver for lan966x Serdes driver Horatiu Vultur
2021-11-16 10:45 ` Vinod Koul
2021-11-16 10:56 ` Horatiu Vultur [this message]
2021-11-16 11:43 ` Vinod Koul
2021-11-16 11:52 ` Horatiu Vultur
2021-11-16 18:12 ` Alexandre Belloni
2021-11-16 22:05 ` Horatiu Vultur
2021-11-23 7:39 ` 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=20211116105601.fauvfv2wzlmcf6jc@soft-dev3-1.localhost \
--to=horatiu.vultur@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=robh+dt@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).