Thread (6 messages) 6 messages, 3 authors, 2026-02-04

Re: [PATCH net-next v4] net: usb: introduce usbnet_mii_ioctl helper function

From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date: 2026-02-03 09:49:33
Also in: linux-usb

On Tue, Feb 03, 2026 at 12:49:57AM -0800, Ethan Nelson-Moore wrote:
On Tue, Feb 3, 2026 at 12:25 AM Andy Shevchenko
[off-list ref] wrote:
quoted
quoted
+extern int usbnet_mii_ioctl(struct net_device *net, struct ifreq *rq, int cmd);
Do we still need to populate 'extern'? Can we get rid of this redundancy?
In my opinion, while you're right that it isn't necessary because all
functions (unlike variables) are implied to be extern, the use of
extern to indicate functions that are exported/intended to be part of
the API is a good idea.
I'm not sure. This makes it harder to read for no benefit. All non-static
functions are part of the API.

-- 
With Best Regards,
Andy Shevchenko

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help