From: Horatiu Vultur - M31836 <Horatiu.Vultur@microchip.com>
To: Parthiban Veerasooran - I17164 <Parthiban.Veerasooran@microchip.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"andrew@lunn.ch" <andrew@lunn.ch>,
"davem@davemloft.net" <davem@davemloft.net>,
"Jan Huber - M16721" <Jan.Huber@microchip.com>,
Thorsten Kummermehr - M21127 <Thorsten.Kummermehr@microchip.com>,
"ramon.nordin.rodriguez@ferroamp.se"
<ramon.nordin.rodriguez@ferroamp.se>
Subject: Re: [PATCH net-next 0/2] add driver support for Microchip LAN865X Rev.B0 Internal PHYs
Date: Thu, 27 Apr 2023 13:24:21 +0200 [thread overview]
Message-ID: <20230427112421.sqnitutjti3yu2yc@soft-dev3-1> (raw)
In-Reply-To: <c1fca21d-00a6-be18-b5b5-4aa5dac94fb3@microchip.com>
The 04/27/2023 07:07, Parthiban Veerasooran - I17164 wrote:
> Hi Horatiu,
>
> On 27/04/23 2:20 am, Horatiu Vultur wrote:
> > The 04/26/2023 17:16, Parthiban Veerasooran wrote:
> >
> > Hi Parthiban,
> >
> > net-next is closed, so please wait until it opens again to send this
> > patch series.
>
> Ah ok, thanks for letting me know.
>
> Do I need to wait until it opens again or shall I continue to fix the
> review comments and sending the next version for the review again until
> the window opens?
Yes, you need to wait until it opens again to send the new version.
Until then, please make sure to answear to all the questions/comments that
you had to the series from all the other people.
> >
> >>
--
/Horatiu
next prev parent reply other threads:[~2023-04-27 11:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 11:46 [PATCH net-next 0/2] add driver support for Microchip LAN865X Rev.B0 Internal PHYs Parthiban Veerasooran
2023-04-26 11:46 ` [PATCH net-next 1/2] net: phy: microchip_t1s: update LAN867x PHY supported revision number Parthiban Veerasooran
2023-04-26 20:56 ` Horatiu Vultur
2023-04-26 11:46 ` [PATCH net-next 2/2] net: phy: microchip_t1s: add support for Microchip LAN865x Rev.B0 PHYs Parthiban Veerasooran
2023-04-26 20:53 ` Ramón Nordin Rodriguez
2023-04-26 21:43 ` Andrew Lunn
2023-04-27 12:28 ` Parthiban.Veerasooran
2023-04-27 14:17 ` Parthiban.Veerasooran
2023-04-26 21:21 ` Horatiu Vultur
2023-04-27 11:28 ` Parthiban.Veerasooran
2023-04-26 21:52 ` Andrew Lunn
2023-04-27 14:19 ` Parthiban.Veerasooran
2023-04-26 22:02 ` Andrew Lunn
2023-04-27 14:23 ` Parthiban.Veerasooran
2023-04-26 20:50 ` [PATCH net-next 0/2] add driver support for Microchip LAN865X Rev.B0 Internal PHYs Horatiu Vultur
2023-04-27 7:07 ` Parthiban.Veerasooran
2023-04-27 11:24 ` Horatiu Vultur - M31836 [this message]
2023-04-27 14:26 ` Parthiban.Veerasooran
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=20230427112421.sqnitutjti3yu2yc@soft-dev3-1 \
--to=horatiu.vultur@microchip.com \
--cc=Jan.Huber@microchip.com \
--cc=Parthiban.Veerasooran@microchip.com \
--cc=Thorsten.Kummermehr@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=ramon.nordin.rodriguez@ferroamp.se \
/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).