From: Dirk Behme <dirk.behme@de.bosch.com>
To: Marko Turk <mt@markoturk.info>, <dakr@kernel.org>,
<linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<rust-for-linux@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] rust: pci: fix typos in Bar struct's comments
Date: Tue, 6 Jan 2026 10:27:17 +0100 [thread overview]
Message-ID: <86b8f2fc-ffe4-40f3-acf9-547e5a5a579d@de.bosch.com> (raw)
In-Reply-To: <20260105213726.73000-2-mt@markoturk.info>
Am 1/5/2026 um 10:37 PM schrieb Marko Turk:
> Fix a typo in the doc-comment of the Bar structure: 'inststance ->
> instance'.
>
> Add also 'is' to the comment inside Bar's `new()` function (suggested
> by Dirk):
> // `pdev` is valid by the invariants of `Device`.
>
> Fixes: bf9651f84b4e ("rust: pci: implement I/O mappable `pci::Bar`")
> Suggested-by: Dirk Behme <dirk.behme@de.bosch.com>
> Signed-off-by: Marko Turk <mt@markoturk.info>
Reviewed-by: Dirk Behme <dirk.behme@de.bosch.com>
Same for patch 1/2.
Thanks!
Dirk
> ---
> Changes since v1:
> - updated commit msg
> - added Fixes: tag
> - fixed another typo as suggested by Dirk
>
> Link to v1: https://lore.kernel.org/lkml/20260103143119.96095-1-mt@markoturk.info/
>
> rust/kernel/pci/io.rs | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/rust/kernel/pci/io.rs b/rust/kernel/pci/io.rs
> index 0d55c3139b6f..82a4f1eba2f5 100644
> --- a/rust/kernel/pci/io.rs
> +++ b/rust/kernel/pci/io.rs
> @@ -20,7 +20,7 @@
> ///
> /// # Invariants
> ///
> -/// `Bar` always holds an `IoRaw` inststance that holds a valid pointer to the start of the I/O
> +/// `Bar` always holds an `IoRaw` instance that holds a valid pointer to the start of the I/O
> /// memory mapped PCI BAR and its size.
> pub struct Bar<const SIZE: usize = 0> {
> pdev: ARef<Device>,
> @@ -54,7 +54,7 @@ pub(super) fn new(pdev: &Device, num: u32, name: &CStr) -> Result<Self> {
> let ioptr: usize = unsafe { bindings::pci_iomap(pdev.as_raw(), num, 0) } as usize;
> if ioptr == 0 {
> // SAFETY:
> - // `pdev` valid by the invariants of `Device`.
> + // `pdev` is valid by the invariants of `Device`.
> // `num` is checked for validity by a previous call to `Device::resource_len`.
> unsafe { bindings::pci_release_region(pdev.as_raw(), num) };
> return Err(ENOMEM);
next prev parent reply other threads:[~2026-01-06 9:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 21:37 [PATCH v2 1/2] rust: io: remove square brackets from pci::Bar reference Marko Turk
2026-01-05 21:37 ` [PATCH v2 2/2] rust: pci: fix typos in Bar struct's comments Marko Turk
2026-01-06 9:27 ` Dirk Behme [this message]
2026-01-06 20:30 ` Danilo Krummrich
2026-01-06 20:49 ` [PATCH v2 1/2] rust: io: remove square brackets from pci::Bar reference Danilo Krummrich
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=86b8f2fc-ffe4-40f3-acf9-547e5a5a579d@de.bosch.com \
--to=dirk.behme@de.bosch.com \
--cc=dakr@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mt@markoturk.info \
--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
all inboxes | Powered by JetHome®