From: Greg KH <email@example.com>
To: Rocco Yue <firstname.lastname@example.org>
Cc: "David S . Miller" <email@example.com>,
Jakub Kicinski <firstname.lastname@example.org>,
Jonathan Corbet <email@example.com>,
Hideaki YOSHIFUJI <firstname.lastname@example.org>,
David Ahern <email@example.com>,
Matthias Brugger <firstname.lastname@example.org>,
Felix Fietkau <email@example.com>, John Crispin <firstname.lastname@example.org>,
Sean Wang <email@example.com>,
Mark Lee <Mark-MC.Lee@mediatek.com>,
Subject: Re: [PATCH 1/4] net: if_arp: add ARPHRD_PUREIP type
Date: Thu, 24 Jun 2021 14:23:30 +0200 [thread overview]
Message-ID: <YNR5QuYqknaZS9firstname.lastname@example.org> (raw)
On Thu, Jun 24, 2021 at 07:53:49PM +0800, Rocco Yue wrote:
> >> +/* exposed API
> >> + * receive incoming datagrams from the Modem and push them to the
> >> + * kernel networking system
> >> + */
> >> +int ccmni_rx_push(unsigned int ccmni_idx, struct sk_buff *skb)
> > Ah, so this driver doesn't really do anything on its own, as there is no
> > modem driver for it.
> > So without a modem driver, it will never be used? Please submit the
> > modem driver at the same time, otherwise it's impossible to review this
> > correctly.
> without MTK ap ccci driver (modem driver), ccmni_rx_push() and
> ccmni_hif_hook() are not be used.
> Both of them are exported as symbols because MTK ap ccci driver
> will be complied to the ccci.ko file.
But I do not see any code in this series that use these symbols. We can
not have exports that no one uses. Please add the driver to this patch
series when you resend it.
> In addition, the code of MTK's modem driver is a bit complicated,
> because this part has more than 30,000 lines of code and contains
> more than 10 modules. We are completeing the upload of this huge
> code step by step. Our original intention was to upload the ccmni
> driver that directly interacts with the kernel first, and then
> complete the code from ccmni to the bottom layer one by one from
> top to bottom. We expect the completion period to be about 1 year.
Again, we can not add code to the kernel that is not used, sorry. That
would not make any sense, would you want to maintain such a thing?
And 30k of code seems a bit excesive for a modem driver. Vendors find
that when they submit code for inclusion in the kernel tree, in the end,
they end up 1/3 the original size, so 10k is reasonable.
I can also take any drivers today into the drivers/staging/ tree, and
you can do the cleanups there as well as getting help from others.
1 year seems like a long time to do "cleanup", good luck!
> > +++ b/drivers/net/ethernet/mediatek/ccmni/ccmni.h
> > Why do you have a .h file for a single .c file? that shouldn't be
> > needed.
> I add a .h file to facilitate subsequent code expansion. If it's
> not appropriate to do this here, I can add the content of .h into
> .c file.
If nothing other than a single .c file needs it, put it into that .c
next prev parent reply other threads:[~2021-06-24 12:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 11:34 [PATCH 1/4] net: if_arp: add ARPHRD_PUREIP type Rocco Yue
2021-06-23 11:34 ` [PATCH 2/4] net: ipv6: don't generate link local address on PUREIP device Rocco Yue
2021-06-23 11:34 ` [PATCH 3/4] net: dev_is_mac_header_xmit() return false for ARPHRD_PUREIP Rocco Yue
2021-06-23 11:34 ` [PATCH 4/4] drivers: net: mediatek: initial implementation of ccmni Rocco Yue
2021-06-23 17:25 ` Greg KH
2021-06-23 17:31 ` Greg KH
2021-06-24 11:53 ` [PATCH 1/4] net: if_arp: add ARPHRD_PUREIP type Rocco Yue
2021-06-24 12:23 ` Greg KH [this message]
2021-06-24 15:55 ` [PATCH 4/4] drivers: net: mediatek: initial implementation of ccmni Rocco Yue
2021-06-24 16:51 ` Greg KH
2021-06-28 7:18 ` Rocco Yue
2021-06-28 9:30 ` Greg KH
2021-06-23 17:19 ` [PATCH 1/4] net: if_arp: add ARPHRD_PUREIP type Greg KH
2021-06-24 3:33 ` Rocco Yue
2021-06-24 5:15 ` David Ahern
2021-06-24 5:31 ` Rocco Yue
2021-06-24 5:29 ` Greg KH
2021-06-24 6:13 ` Rocco Yue
2021-06-24 9:04 ` Greg KH
2021-06-24 12:24 ` Rocco Yue
2021-06-24 13:06 ` Greg KH
2021-06-25 6:01 ` Rocco Yue
2021-06-24 16:14 ` Dan Williams
2021-06-25 6:04 ` Rocco Yue
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).