From: "Alvin Šipraga" <ALSI@bang-olufsen.dk>
To: Luiz Angelo Daros de Luca <luizluca@gmail.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"andrew@lunn.ch" <andrew@lunn.ch>,
"vivien.didelot@gmail.com" <vivien.didelot@gmail.com>,
"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
"olteanv@gmail.com" <olteanv@gmail.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"kuba@kernel.org" <kuba@kernel.org>,
"arinc.unal@arinc9.com" <arinc.unal@arinc9.com>
Subject: Re: [PATCH net-next v3 1/2] net: dsa: tag_rtl8_4: add rtl8_4t trailing variant
Date: Wed, 23 Feb 2022 14:54:39 +0000 [thread overview]
Message-ID: <8735k9fxao.fsf@bang-olufsen.dk> (raw)
In-Reply-To: <20220222224758.11324-2-luizluca@gmail.com> (Luiz Angelo Daros de Luca's message of "Tue, 22 Feb 2022 19:47:57 -0300")
Luiz Angelo Daros de Luca <luizluca@gmail.com> writes:
> Realtek switches supports the same tag both before ethertype or between
> payload and the CRC.
>
> Signed-off-by: Luiz Angelo Daros de Luca <luizluca@gmail.com>
> ---
> include/net/dsa.h | 2 +
> net/dsa/tag_rtl8_4.c | 154 +++++++++++++++++++++++++++++++++----------
> 2 files changed, 121 insertions(+), 35 deletions(-)
Reviewed-by: Alvin Šipraga <alsi@bang-olufsen.dk>
next prev parent reply other threads:[~2022-02-23 14:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 22:47 [PATCH net-next v3 0/2] net: dsa: realtek: add rtl8_4t tag Luiz Angelo Daros de Luca
2022-02-22 22:47 ` [PATCH net-next v3 1/2] net: dsa: tag_rtl8_4: add rtl8_4t trailing variant Luiz Angelo Daros de Luca
2022-02-23 14:54 ` Alvin Šipraga [this message]
2022-02-24 0:04 ` Vladimir Oltean
2022-02-25 6:10 ` Luiz Angelo Daros de Luca
2022-02-22 22:47 ` [PATCH net-next v3 2/2] net: dsa: realtek: rtl8365mb: add support for rtl8_4t Luiz Angelo Daros de Luca
2022-02-23 14:58 ` Alvin Šipraga
2022-02-23 23:43 ` [PATCH net-next v3 0/2] net: dsa: realtek: add rtl8_4t tag Vladimir Oltean
2022-02-25 5:16 ` 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=8735k9fxao.fsf@bang-olufsen.dk \
--to=alsi@bang-olufsen.dk \
--cc=andrew@lunn.ch \
--cc=arinc.unal@arinc9.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=luizluca@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.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;
as well as URLs for NNTP newsgroup(s).