All of lore.kernel.org
 help / color / mirror / Atom feed
From: Taotao Chen <chentaotao@didiglobal.com>
To: <a.hindborg@kernel.org>
Cc: <bjorn3_gh@protonmail.com>, <boqun.feng@gmail.com>,
	<chentao325@qq.com>, <linux-kernel@vger.kernel.org>,
	<rust-for-linux@vger.kernel.org>
Subject: [PATCH v2] rust: block: Remove unnecessary comma in introduction
Date: Fri, 21 Mar 2025 13:22:08 +0800	[thread overview]
Message-ID: <Z9z3gCdqa+GN91SA@OneApple> (raw)

The comma before "methods" was not needed and has been removed
for better readability and correctness.

Signed-off-by: Taotao Chen <chentaotao@didiglobal.com>
---
 v1 -> v2 : Corrected message: removed comma was before "methods" not after.
 rust/kernel/block/mq.rs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/rust/kernel/block/mq.rs b/rust/kernel/block/mq.rs
index fb0f393c1cea..ee8f34f40899 100644
--- a/rust/kernel/block/mq.rs
+++ b/rust/kernel/block/mq.rs
@@ -23,7 +23,7 @@
 //! IO requests are passed to the driver as [`kernel::types::ARef<Request>`]
 //! instances. The `Request` type is a wrapper around the C `struct request`.
 //! The driver must mark end of processing by calling one of the
-//! `Request::end`, methods. Failure to do so can lead to deadlock or timeout
+//! `Request::end` methods. Failure to do so can lead to deadlock or timeout
 //! errors. Please note that the C function `blk_mq_start_request` is implicitly
 //! called when the request is queued with the driver.
 //!
-- 
2.34.1


             reply	other threads:[~2025-03-21  5:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-21  5:22 Taotao Chen [this message]
2025-03-23 12:25 ` [PATCH v2] rust: block: Remove unnecessary comma in introduction 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=Z9z3gCdqa+GN91SA@OneApple \
    --to=chentaotao@didiglobal.com \
    --cc=a.hindborg@kernel.org \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=chentao325@qq.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.