linux-kernel - Re: linux-next: build warning after merge of the usb tree

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: <2024010816-fabric-cassette-1548@gregkh>
Date: Mon, 8 Jan 2024 08:54:39 +0100
From: Greg KH <greg@...ah.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
	Krishna Kurapati <quic_kriskura@...cinc.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build warning after merge of the usb tree

On Mon, Jan 08, 2024 at 04:02:21PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the usb tree, today's linux-next build (htmldocs) produced
> this warning:
> 
> Documentation/usb/gadget-testing.rst:459: ERROR: Malformed table.
> Text in column margin in table line 9.
> 
> ===============   ==================================================
> ifname            network device interface name associated with this
>                   function instance
> qmult             queue length multiplier for high and super speed
> host_addr         MAC address of host's end of this
>                   Ethernet over USB link
> dev_addr          MAC address of device's end of this
>                   Ethernet over USB link
> max_segment_size  Segment size required for P2P connections. This
>                   will set MTU to (max_segment_size - 14 bytes)
> ===============   ==================================================
> 
> Introduced by commit
> 
>   1900daeefd3e ("usb: gadget: ncm: Add support to update wMaxSegmentSize via configfs")

Krishna, can you send a fixup patch for this?

thanks,

greg k-h