From: Leon Romanovsky <leon@kernel.org>
To: tianx <tianx@yunsilicon.com>
Cc: Andrew Lunn <andrew@lunn.ch>, weihonggang <weihg@yunsilicon.com>,
netdev@vger.kernel.org, andrew+netdev@lunn.ch, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com, davem@davemloft.net,
jeff.johnson@oss.qualcomm.com, przemyslaw.kitszel@intel.com,
wanry@yunsilicon.com
Subject: Re: [PATCH v2 08/14] net-next/yunsilicon: Add ethernet interface
Date: Tue, 31 Dec 2024 13:34:12 +0200 [thread overview]
Message-ID: <20241231113412.GC81460@unreal> (raw)
In-Reply-To: <a09b9cda-5961-452b-84cb-844262e5b71a@yunsilicon.com>
On Tue, Dec 31, 2024 at 05:40:15PM +0800, tianx wrote:
> On 2024/12/31 13:12, Andrew Lunn wrote:
> > On Tue, Dec 31, 2024 at 12:13:23AM +0800, weihonggang wrote:
> >> Andrew, In another module(xsc_pci), we check xdev_netdev is NULL or not
> >> to see whether network module(xsc_eth) is loaded. we do not care about
> >> the real type,and we do not want to include the related header files in
> >> other modules. so we use the void type.
> > Please don't top post.
> >
> > If all you care about is if the module is loaded, turn it into a bool,
> > and set it true.
> >
> > Andrew
>
> Hi, Andrew
>
> Not only the PCI module, but our later RDMA module also needs the netdev
> structure in xsc_core_device to access network information. To simplify
> the review, we haven't submitted the RDMA module, but keeping the netdev
> helps avoid repeated changes when submitting later.
Don't worry about RDMA at this point, your driver structure doesn't fit
current multi-subsystem design.
You will need to completely rewrite your "net-next/yunsilicon: Device and
interface management" patch anyway when you will send us RDMA part.
Please use auxiliary bus infrastructure to split your driver to separate
it separate modules, instead of reinventing it.
Thanks
>
> Best regards,
>
> Xin
>
next prev parent reply other threads:[~2024-12-31 11:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-30 10:15 [PATCH v2 00/14] net-next/yunsilicon: ADD Yunsilicon XSC Ethernet Driver Xin Tian
2024-12-30 10:15 ` [PATCH v2 01/14] net-next/yunsilicon: Add xsc driver basic framework Xin Tian
2024-12-30 10:15 ` [PATCH v2 02/14] net-next/yunsilicon: Enable CMDQ Xin Tian
2024-12-30 10:15 ` [PATCH v2 03/14] net-next/yunsilicon: Add hardware setup APIs Xin Tian
2024-12-30 10:15 ` [PATCH v2 04/14] net-next/yunsilicon: Add qp and cq management Xin Tian
2024-12-30 10:15 ` [PATCH v2 05/14] net-next/yunsilicon: Add eq and alloc Xin Tian
2024-12-30 10:15 ` [PATCH v2 06/14] net-next/yunsilicon: Add pci irq Xin Tian
2024-12-30 10:15 ` [PATCH v2 07/14] net-next/yunsilicon: Device and interface management Xin Tian
2024-12-30 10:15 ` [PATCH v2 08/14] net-next/yunsilicon: Add ethernet interface Xin Tian
2024-12-30 15:29 ` Andrew Lunn
2024-12-30 16:13 ` weihonggang
2024-12-31 5:12 ` Andrew Lunn
2024-12-31 9:28 ` weihonggang
2024-12-31 9:40 ` tianx
2024-12-31 11:34 ` Leon Romanovsky [this message]
2025-01-03 3:16 ` tianx
2024-12-31 15:40 ` Andrew Lunn
2025-01-03 3:28 ` tianx
2024-12-30 10:15 ` [PATCH v2 09/14] net-next/yunsilicon: Init net device Xin Tian
2024-12-30 10:15 ` [PATCH v2 10/14] net-next/yunsilicon: Add eth needed qp and cq apis Xin Tian
2024-12-30 10:15 ` [PATCH v2 11/14] net-next/yunsilicon: ndo_open and ndo_stop Xin Tian
2024-12-30 10:15 ` [PATCH v2 12/14] net-next/yunsilicon: Add ndo_start_xmit Xin Tian
2024-12-30 10:15 ` [PATCH v2 13/14] net-next/yunsilicon: Add eth rx Xin Tian
2024-12-30 10:15 ` [PATCH v2 14/14] net-next/yunsilicon: add ndo_get_stats64 Xin Tian
2024-12-31 1:11 ` [PATCH v2 00/14] net-next/yunsilicon: ADD Yunsilicon XSC Ethernet Driver Jakub Kicinski
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=20241231113412.GC81460@unreal \
--to=leon@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=tianx@yunsilicon.com \
--cc=wanry@yunsilicon.com \
--cc=weihg@yunsilicon.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).