From: Benno Lossin <benno.lossin@proton.me>
To: Dirk Behme <dirk.behme@de.bosch.com>, rust-for-linux@vger.kernel.org
Subject: Re: [PATCH] docs: rust: Add rusttest info
Date: Thu, 07 Dec 2023 19:43:06 +0000 [thread overview]
Message-ID: <37cfa972-c2ad-4779-bc4f-db4cf561bee1@proton.me> (raw)
In-Reply-To: <20231206125736.2040066-1-dirk.behme@de.bosch.com>
On 12/6/23 13:57, Dirk Behme wrote:
> Searching the Rust kernel documentation all existing Rust Make
> targets (rustavailable, rustfmt, rustfmtcheck, rustdoc and
> rust-analyzer) are explicitly documented with their Make syntax.
> While the Make target rusttest is mentioned two times in the
> existing documentation, it's Make syntax is not explicitly
> documented, yet. Add a test section to document this.
>
> Signed-off-by: Dirk Behme <dirk.behme@de.bosch.com>
> ---
> Documentation/rust/general-information.rst | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/Documentation/rust/general-information.rst b/Documentation/rust/general-information.rst
> index 081397827a7ea..af9812ce11d7b 100644
> --- a/Documentation/rust/general-information.rst
> +++ b/Documentation/rust/general-information.rst
> @@ -77,3 +77,13 @@ configuration:
> #[cfg(CONFIG_X="y")] // Enabled as a built-in (`y`)
> #[cfg(CONFIG_X="m")] // Enabled as a module (`m`)
> #[cfg(not(CONFIG_X))] // Disabled
> +
> +Testing
> +-------
> +
> +Running the Rust tests the Make target is::
This sentence sounds a bit weird to me, how about
To run the Rust tests, you can use the following make target::
--
Cheers,
Benno
next prev parent reply other threads:[~2023-12-07 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 12:57 [PATCH] docs: rust: Add rusttest info Dirk Behme
2023-12-07 19:43 ` Benno Lossin [this message]
2023-12-08 5:31 ` Trevor Gross
2023-12-08 12:27 ` Miguel Ojeda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=37cfa972-c2ad-4779-bc4f-db4cf561bee1@proton.me \
--to=benno.lossin@proton.me \
--cc=dirk.behme@de.bosch.com \
--cc=rust-for-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).