From: Justin Lai <justinlai0215@realtek.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: "kuba@kernel.org" <kuba@kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: RE: [PATCH net-next v5 1/2] net/ethernet/realtek: Add Realtek automotive PCIe driver code
Date: Mon, 21 Aug 2023 13:38:12 +0000 [thread overview]
Message-ID: <371e0e25bee34ad7bf6f9fa44713ac1b@realtek.com> (raw)
In-Reply-To: <ZN9g+dwZcqaX8hTO@nanopsycho>
> Fri, Aug 18, 2023 at 01:55:00PM CEST, justinlai0215@realtek.com wrote:
> V>This patch is to add the ethernet device driver for the PCIe interface
> V>of Realtek Automotive Ethernet Switch,
> >applicable to RTL9054, RTL9068, RTL9072, RTL9075, RTL9068, RTL9071.
> >
> >Below is a simplified block diagram of the chip and its relevant interfaces.
> >
> > *************************
> > * *
> > * CPU network device *
> > * ____________ *
> > * | | *
> > * | PCIE Host | *
> > *************************
> > ||
> > PCIE
> > ||
> > ****************************************
> > * | PCIE Endpoint | *
> > * |---------------| *
> > * | GMAC | *
> > * |------| Realtek *
> > * || RTL90xx Series *
> > * || *
> > * _____________||______________ *
> > * | |MAC| | *
> > * | |---| | *
> > * | | *
> > * | Ethernet Switch Core | *
> > * | | *
> > * | ----- ----- | *
> > * | |MAC| ............|MAC| | *
> > * |__|___|_____________|___|____| *
> > * |PHY| ............|PHY| *
> > * ----- ----- *
> > *********||****************||***********
> >
> >The block of the Realtek RTL90xx series is our entire chip
> >architecture, the GMAC is connected to the switch core, and there is no
> >PHY in between. In addition, this driver is mainly used to control GMAC, but
> does not control the switch core, so it is not the same as DSA.
>
> [..]
>
>
> >+
> >+#define NETIF_F_ALL_CSUM NETIF_F_CSUM_MASK
> >+
> >+#define NETIF_F_HW_VLAN_RX NETIF_F_HW_VLAN_CTAG_RX #define
> >+NETIF_F_HW_VLAN_TX NETIF_F_HW_VLAN_CTAG_TX
>
> [..]
>
> I see 3 essentials wrong from 10sec review:
> 1) You don't cc people who commented your previous versions
> 2) You don't respect 72cols for patch description text (checkpatch did
> warn you, didn't it?)
> 3) You are defining very odd macros like these 3
>
> No need to read any longer... Really, can't you please ask someone who knows
> to help you with the submission preparation? You are vasting time of people :/
>
Thank you for your reply, I will re-check this driver and the content you mentioned above.
next prev parent reply other threads:[~2023-08-21 13:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 11:54 [PATCH net-next v5 0/2] Add Realtek automotive PCIe driver Justin Lai
2023-08-18 11:55 ` [PATCH net-next v5 1/2] net/ethernet/realtek: Add Realtek automotive PCIe driver code Justin Lai
2023-08-18 12:15 ` Jiri Pirko
2023-08-21 13:38 ` Justin Lai [this message]
2023-08-18 11:55 ` [PATCH net-next v5 2/2] MAINTAINERS: Add the rtase ethernet driver entry Justin Lai
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=371e0e25bee34ad7bf6f9fa44713ac1b@realtek.com \
--to=justinlai0215@realtek.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).