linux-kernel - Re: linux-next: build warning for a long time

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2024101127-scrubbed-unfilled-8b47@gregkh>
Date: Fri, 11 Oct 2024 08:31:47 +0200
From: Greg KH <greg@...ah.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Jonathan Corbet <corbet@....net>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build warning for a long time

On Fri, Oct 11, 2024 at 05:24:42PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> From before the git era, an htmldocs build (if we had such a thing back
> then) would complain like this:
> 
> Documentation/driver-api/usb/usb:164: drivers/usb/core/message.c:968: WARNING: Duplicate C declaration, also defined at driver-api/usb/gadget:804.
> Declaration is '.. c:function:: int usb_string (struct usb_device *dev, int index, char *buf, size_t size)'.
> 
> I assume it is confused because we have documented both a function and a
> data type called "usb_string".  The former in drivers/usb/core/message.c
> and the latter in include/linux/usb/gadget.h.
> 
> There are about 46 references to the function and 105 to the struct.
> We could rename the function to usb_string_utf8 ...

But usb strings are not in utf8 format :)

As C can handle this just fine, odds are sphinx should also be able to
handle this?

thanks,

greg k-h