public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: "Alvin Šipraga" <ALSI@bang-olufsen.dk>
Cc: "Alvin Šipraga" <alvin@pqrs.dk>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"hauke@hauke-m.de" <hauke@hauke-m.de>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Andrew Lunn" <andrew@lunn.ch>,
	"Vivien Didelot" <vivien.didelot@gmail.com>,
	"Florian Fainelli" <f.fainelli@gmail.com>,
	"Vladimir Oltean" <olteanv@gmail.com>,
	"Eric Dumazet" <edumazet@google.com>,
	"Paolo Abeni" <pabeni@redhat.com>,
	"Russell King" <linux@armlinux.org.uk>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v2 0/5] net: dsa: realtek: rtl8365mb: improve handling of PHY modes
Date: Wed, 15 Jun 2022 15:21:27 -0700	[thread overview]
Message-ID: <20220615152127.0d530fe4@kernel.org> (raw)
In-Reply-To: <20220615165529.3g6aqwdpwxqhs6nj@bang-olufsen.dk>

On Wed, 15 Jun 2022 16:55:29 +0000 Alvin Šipraga wrote:
> David, Jakub, this series is marked Changes Requested on patchwork, but I have
> addressed all the comments. Do you want me to resend?

Oh, that was me. I was hoping you'd respin to at least clarify 
the commit message on patch 5, based on Russell's questions.
Perhaps that's not as important these days given we add Links
to the original discussion but should be useful to person reading 
just the git history. Sorry for not making that clear, folks sending
comments and still acking the patch in general gives me low signal.

  reply	other threads:[~2022-06-15 22:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10 15:38 [PATCH net-next v2 0/5] net: dsa: realtek: rtl8365mb: improve handling of PHY modes Alvin Šipraga
2022-06-10 15:38 ` [PATCH net-next v2 1/5] net: dsa: realtek: rtl8365mb: rename macro RTL8367RB -> RTL8367RB_VB Alvin Šipraga
2022-06-10 15:38 ` [PATCH net-next v2 2/5] net: dsa: realtek: rtl8365mb: remove port_mask private data member Alvin Šipraga
2022-06-10 15:38 ` [PATCH net-next v2 3/5] net: dsa: realtek: rtl8365mb: correct the max number of ports Alvin Šipraga
2022-06-10 15:38 ` [PATCH net-next v2 4/5] net: dsa: realtek: rtl8365mb: remove learn_limit_max private data member Alvin Šipraga
2022-06-12  1:40   ` Luiz Angelo Daros de Luca
2022-06-12 10:56     ` Alvin Šipraga
2022-06-10 15:38 ` [PATCH net-next v2 5/5] net: dsa: realtek: rtl8365mb: handle PHY interface modes correctly Alvin Šipraga
2022-06-10 16:36   ` Russell King (Oracle)
2022-06-10 17:45     ` Alvin Šipraga
2022-06-12  3:20   ` Luiz Angelo Daros de Luca
2022-06-15 16:55 ` [PATCH net-next v2 0/5] net: dsa: realtek: rtl8365mb: improve handling of PHY modes Alvin Šipraga
2022-06-15 22:21   ` Jakub Kicinski [this message]
2022-06-15 22:32     ` Alvin Šipraga

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=20220615152127.0d530fe4@kernel.org \
    --to=kuba@kernel.org \
    --cc=ALSI@bang-olufsen.dk \
    --cc=alvin@pqrs.dk \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=hauke@hauke-m.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=vivien.didelot@gmail.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