The Linux Kernel Mailing List
 help / color / mirror / Atom feed
* [PATCH] block: Fix typo in comment
@ 2026-05-07 10:58 Md Shofiqul Islam
  2026-05-07 11:11 ` Jens Axboe
  0 siblings, 1 reply; 2+ messages in thread
From: Md Shofiqul Islam @ 2026-05-07 10:58 UTC (permalink / raw)
  To: axboe; +Cc: linux-block, linux-kernel, Md Shofiqul Islam

Fix a typo in a comment in bio_split_alignment(): "occured" should
be "occurred".

Signed-off-by: Md Shofiqul Islam <shofiqtest@gmail.com>
---
 block/blk-merge.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/block/blk-merge.c b/block/blk-merge.c
index fcf09325b2..395b23ed95 100644
--- a/block/blk-merge.c
+++ b/block/blk-merge.c
@@ -403,7 +403,7 @@ int bio_split_io_at(struct bio *bio, const struct queue_limits *lim,
 	 * there may either be too many discontiguous vectors for the max
 	 * segments limit, or contain virtual boundary gaps without having a
 	 * valid block sized split. A zero byte result means one of those
-	 * conditions occured.
+	 * conditions occurred.
 	 */
 	bytes = ALIGN_DOWN(bytes, bio_split_alignment(bio, lim));
 	if (!bytes)
-- 
2.54.0.windows.1


^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH] block: Fix typo in comment
  2026-05-07 10:58 [PATCH] block: Fix typo in comment Md Shofiqul Islam
@ 2026-05-07 11:11 ` Jens Axboe
  0 siblings, 0 replies; 2+ messages in thread
From: Jens Axboe @ 2026-05-07 11:11 UTC (permalink / raw)
  To: Md Shofiqul Islam; +Cc: linux-block, linux-kernel

On 5/7/26 4:58 AM, Md Shofiqul Islam wrote:
> Fix a typo in a comment in bio_split_alignment(): "occured" should
> be "occurred".
> 
> Signed-off-by: Md Shofiqul Islam <shofiqtest@gmail.com>
> ---
>  block/blk-merge.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/block/blk-merge.c b/block/blk-merge.c
> index fcf09325b2..395b23ed95 100644
> --- a/block/blk-merge.c
> +++ b/block/blk-merge.c
> @@ -403,7 +403,7 @@ int bio_split_io_at(struct bio *bio, const struct queue_limits *lim,
>  	 * there may either be too many discontiguous vectors for the max
>  	 * segments limit, or contain virtual boundary gaps without having a
>  	 * valid block sized split. A zero byte result means one of those
> -	 * conditions occured.
> +	 * conditions occurred.

Generally happy to take typo fixes if they come with real fixes too,
otherwise it's just unnecessary churn that potentially causes stable
backport issues.

-- 
Jens Axboe


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2026-05-07 11:12 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-05-07 10:58 [PATCH] block: Fix typo in comment Md Shofiqul Islam
2026-05-07 11:11 ` Jens Axboe

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox