From: Andreas Hindborg <a.hindborg@samsung.com>
To: Miguel Ojeda <ojeda@kernel.org>
Cc: "Masahiro Yamada" <masahiroy@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Carlos Bilbao" <carlos.bilbao@amd.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Alice Ryhl" <aliceryhl@google.com>,
"linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"rust-for-linux@vger.kernel.org" <rust-for-linux@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"patches@lists.linux.dev" <patches@lists.linux.dev>,
"Akira Yokosawa" <akiyks@gmail.com>,
"Martin Rodriguez Reboredo" <yakoyoku@gmail.com>
Subject: Re: [PATCH 1/2] docs: rust: update Rust docs output path
Date: Thu, 19 Oct 2023 12:03:03 +0000 [thread overview]
Message-ID: <87wmviizv2.fsf@samsung.com> (raw)
In-Reply-To: <20231018160145.1017340-1-ojeda@kernel.org>
Miguel Ojeda <ojeda@kernel.org> writes:
> The Rust code documentation output path moved from `rust/doc` to
> `Documentation/output/rust/rustdoc`, thus update the old reference.
>
> Fixes: 48fadf440075 ("docs: Move rustdoc output, cross-reference it")
> Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
Reviewed-by: Andreas Hindborg <a.hindborg@samsung.com>
> ---
> Documentation/rust/general-information.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/rust/general-information.rst b/Documentation/rust/general-information.rst
> index 49029ee82e55..081397827a7e 100644
> --- a/Documentation/rust/general-information.rst
> +++ b/Documentation/rust/general-information.rst
> @@ -29,7 +29,7 @@ target with the same invocation used for compilation, e.g.::
>
> To read the docs locally in your web browser, run e.g.::
>
> - xdg-open rust/doc/kernel/index.html
> + xdg-open Documentation/output/rust/rustdoc/kernel/index.html
>
> To learn about how to write the documentation, please see coding-guidelines.rst.
>
>
> base-commit: 8a749fd1a8720d4619c91c8b6e7528c0a355c0aa
next prev parent reply other threads:[~2023-10-19 12:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20231018160207eucas1p1db839e2eb9a2ad39013c08c0e6f4624e@eucas1p1.samsung.com>
2023-10-18 16:01 ` [PATCH 1/2] docs: rust: update Rust docs output path Miguel Ojeda
2023-10-18 16:01 ` [PATCH 2/2] kbuild: remove old " Miguel Ojeda
2023-10-18 17:56 ` Benno Lossin
2023-10-18 21:51 ` Alice Ryhl
2023-10-19 12:03 ` Andreas Hindborg
2023-10-23 14:43 ` Carlos Bilbao
2023-10-18 17:55 ` [PATCH 1/2] docs: rust: update " Benno Lossin
2023-10-18 21:50 ` Alice Ryhl
2023-10-18 22:57 ` Miguel Ojeda
2023-10-19 12:03 ` Andreas Hindborg [this message]
2023-10-23 14:43 ` Carlos Bilbao
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=87wmviizv2.fsf@samsung.com \
--to=a.hindborg@samsung.com \
--cc=akiyks@gmail.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=carlos.bilbao@amd.com \
--cc=corbet@lwn.net \
--cc=gary@garyguo.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=ojeda@kernel.org \
--cc=patches@lists.linux.dev \
--cc=rust-for-linux@vger.kernel.org \
--cc=wedsonaf@gmail.com \
--cc=yakoyoku@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.