From: Shannon Sterz <s.sterz@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox] tree-wide: fix private intra doc links
Date: Thu, 6 Mar 2025 17:06:18 +0100 [thread overview]
Message-ID: <20250306160618.473818-1-s.sterz@proxmox.com> (raw)
a previous commit fixed up all intra doc links that were present on
public apis, this also fixes the links for private members.
Signed-off-by: Shannon Sterz <s.sterz@proxmox.com>
---
proxmox-io/src/sparse_copy.rs | 4 ++--
proxmox-rest-server/src/worker_task.rs | 2 +-
proxmox-sys/src/fs/file.rs | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/proxmox-io/src/sparse_copy.rs b/proxmox-io/src/sparse_copy.rs
index fad1a51a..400fe51a 100644
--- a/proxmox-io/src/sparse_copy.rs
+++ b/proxmox-io/src/sparse_copy.rs
@@ -26,8 +26,8 @@ pub struct SparseCopyResult {
pub seeked_last: bool,
}
-/// Copy similar to [`io::copy`](std::io::copy), but seeks the target when encountering zero bytes
-/// instead of writing them.
+/// Copy similar to [`io::copy`], but seeks the target when encountering zero bytes instead of
+/// writing them.
///
/// Example use:
/// ```
diff --git a/proxmox-rest-server/src/worker_task.rs b/proxmox-rest-server/src/worker_task.rs
index 6368206c..103749ac 100644
--- a/proxmox-rest-server/src/worker_task.rs
+++ b/proxmox-rest-server/src/worker_task.rs
@@ -50,7 +50,7 @@ pub fn check_last_worker() {
}
/// Spawn a task which calls [`check_last_worker()`] in the case of a requested shutdown. This used
-/// to be implied by the [`request_shutdown()`] call when it was part of the `proxmox-rest-server`
+/// to be implied by the `request_shutdown()` call when it was part of the `proxmox-rest-server`
/// crate, which is no longer the case.
fn check_workers_on_shutdown() {
tokio::spawn(async {
diff --git a/proxmox-sys/src/fs/file.rs b/proxmox-sys/src/fs/file.rs
index 74b9e74e..1f8f9697 100644
--- a/proxmox-sys/src/fs/file.rs
+++ b/proxmox-sys/src/fs/file.rs
@@ -117,7 +117,7 @@ pub fn file_read_firstline<P: AsRef<Path>>(path: P) -> Result<String, Error> {
}
#[inline]
-/// Creates a tmpfile like [`nix::unistd::mkstemp`], but with [`nix::fctnl::Oflag`] set.
+/// Creates a tmpfile like [`nix::unistd::mkstemp`], but with [`OFlag`] set.
///
/// Note that some flags are masked out since they can produce an error, see mkostemp(2) for details.
// code is mostly copied from nix mkstemp
--
2.39.5
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next reply other threads:[~2025-03-06 16:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 16:06 Shannon Sterz [this message]
2025-03-07 10:35 ` [pbs-devel] applied: " Thomas Lamprecht
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=20250306160618.473818-1-s.sterz@proxmox.com \
--to=s.sterz@proxmox.com \
--cc=pbs-devel@lists.proxmox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal