[PATCH 1/4] net: if_arp: add ARPHRD_PUREIP type
gregkh at linuxfoundation.org
Thu Jun 24 05:23:30 PDT 2021
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
More information about the Linux-mediatek