[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <183d4a59-acf1-4784-8194-da8e484ccb1b@lunn.ch>
Date: Mon, 9 Oct 2023 15:54:47 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: FUJITA Tomonori <fujita.tomonori@...il.com>, netdev@...r.kernel.org,
rust-for-linux@...r.kernel.org, greg@...ah.com, tmgross@...ch.edu,
Wedson Almeida Filho <wedsonaf@...il.com>
Subject: Re: [PATCH net-next v3 1/3] rust: core abstractions for network PHY
drivers
> > +/// This is used by [`module_phy_driver`] macro to create a static array of phy_driver`.
>
> Broken formatting? Does `rustdoc` complain about it?
For C code, when you do a kernel build with W=1, it enables the
kerneldoc checker on each file:
e.g:
./scripts/kernel-doc -none arch/x86/entry/vdso/vdso-image-32.c
Can rustdoc be invoked in a similar way? Perform a check on a file,
issue errors, but don't actually generate any documentation? If it
can, it would be good to extend W=1 with this.
The netdev CI instance builds with W=1, so we get to see problems like
this, and we ask for it to be fixed up before the code is merged.
Andrew
Powered by blists - more mailing lists