From: Vladimir Oltean <olteanv@gmail.com>
To: "Alvin Šipraga" <ALSI@bang-olufsen.dk>
Cc: Luiz Angelo Daros de Luca <luizluca@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"andrew@lunn.ch" <andrew@lunn.ch>,
"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"arinc.unal@arinc9.com" <arinc.unal@arinc9.com>
Subject: Re: [PATCH net-next 4/7] net: dsa: realtek: create realtek-common
Date: Mon, 11 Dec 2023 19:19:37 +0200 [thread overview]
Message-ID: <20231211171937.zb2rw2i7um4s5vnn@skbuf> (raw)
In-Reply-To: <255k4l2u45si3k2o7ulcjaej7k56cgacut6lacumobywzvycm5@vvpswdlqt2gs>
On Mon, Dec 11, 2023 at 09:24:35AM +0000, Alvin Šipraga wrote:
> Yes, it is exhausting with this back and forth. Please just address what
> you are willing to address and I will review again. Thanks.
Alvin, I really appreciate the time you've put into reviewing this.
It is very helpful to have you around.
next prev parent reply other threads:[~2023-12-11 17:19 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 4:41 [PATCH net-next 0/7] net: dsa: realtek: variants to drivers, interfaces to a common module Luiz Angelo Daros de Luca
2023-12-08 4:41 ` [PATCH net-next 1/7] net: dsa: realtek: drop cleanup from realtek_priv Luiz Angelo Daros de Luca
2023-12-08 9:49 ` Alvin Šipraga
2023-12-08 4:41 ` [PATCH net-next 2/7] net: dsa: realtek: put of node after MDIO registration Luiz Angelo Daros de Luca
2023-12-08 5:13 ` Luiz Angelo Daros de Luca
2023-12-08 9:49 ` Alvin Šipraga
2023-12-08 18:05 ` Luiz Angelo Daros de Luca
2023-12-11 17:11 ` Vladimir Oltean
2023-12-12 3:47 ` Luiz Angelo Daros de Luca
2023-12-12 21:58 ` Vladimir Oltean
2023-12-13 4:37 ` Luiz Angelo Daros de Luca
2023-12-13 13:04 ` Vladimir Oltean
2023-12-16 4:26 ` Luiz Angelo Daros de Luca
2023-12-08 4:41 ` [PATCH net-next 3/7] net: dsa: realtek: convert variants into a real driver Luiz Angelo Daros de Luca
2023-12-08 10:23 ` Alvin Šipraga
2023-12-08 4:41 ` [PATCH net-next 4/7] net: dsa: realtek: create realtek-common Luiz Angelo Daros de Luca
2023-12-08 5:01 ` Luiz Angelo Daros de Luca
2023-12-08 10:52 ` Alvin Šipraga
2023-12-11 5:02 ` Luiz Angelo Daros de Luca
2023-12-11 9:44 ` Alvin Šipraga
2023-12-08 14:02 ` Alvin Šipraga
2023-12-11 5:02 ` Luiz Angelo Daros de Luca
2023-12-11 9:24 ` Alvin Šipraga
2023-12-11 17:19 ` Vladimir Oltean [this message]
2023-12-08 4:41 ` [PATCH net-next 5/7] net: dsa: realtek: merge interface modules into common Luiz Angelo Daros de Luca
2023-12-08 10:57 ` Alvin Šipraga
2023-12-11 5:13 ` Luiz Angelo Daros de Luca
2023-12-11 9:25 ` Alvin Šipraga
2023-12-08 4:41 ` [PATCH net-next 6/7] net: dsa: realtek: migrate user_mii setup to common Luiz Angelo Daros de Luca
2023-12-08 11:05 ` Alvin Šipraga
2023-12-11 5:16 ` Luiz Angelo Daros de Luca
2023-12-08 4:41 ` [PATCH net-next 7/7] net: dsa: realtek: always use the realtek user mdio driver Luiz Angelo Daros de Luca
2023-12-08 11:06 ` Alvin Šipraga
2023-12-11 5:29 ` Luiz Angelo Daros de Luca
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=20231211171937.zb2rw2i7um4s5vnn@skbuf \
--to=olteanv@gmail.com \
--cc=ALSI@bang-olufsen.dk \
--cc=andrew@lunn.ch \
--cc=arinc.unal@arinc9.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=luizluca@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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