[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2025091624-mud-scotch-4c1a@gregkh>
Date: Tue, 16 Sep 2025 20:30:09 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Tong <djfkvcing117@...il.com>
Cc: linux-kernel@...r.kernel.org, rust-for-linux@...r.kernel.org,
onur-ozkan <work@...rozkan.dev>
Subject: Re: [PATCH] rust/fs: use intra-doc link for `EBADF` in `BadFdError`
docs
On Wed, Sep 17, 2025 at 01:13:38AM +0800, Tong wrote:
> >From af7f05e99ed67f57c83e51ca3a1b3010e3e87762 Mon Sep 17 00:00:00 2001
> From: tong <djfkvcing117@...il.com>
> Date: Wed, 17 Sep 2025 00:25:44 +0800
> Subject: [PATCH] rust/fs: use intra-doc link for `EBADF` in `BadFdError` docs
> MIME-Version: 1.0
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 8bit
Perhaps try using git send-email? That way this will not show up in the
body of the message.
> In rust/kernel/fs/file.rs, replace plain-text `EBADF` in the doc
> comment for BadFdError with an intra-doc link [`EBADF`].
>
> This improves the generated documentation (so the `EBADF` constant is
> linked), and helps tools such as rust-analyzer to resolve such
> references from the docs.
>
> Suggested-by: Onur Özkan <work@...rozkan.dev>
> Link: https://github.com/Rust-for-Linux/linux/issues/1186
> Signed-off-by: tong <djfkvcing117@...il.com>
We need a full name please.
thanks,
greg k-h
Powered by blists - more mailing lists