From: Christophe JAILLET <[email protected]>
To: Thorsten Blum <[email protected]>, [email protected]
Cc: [email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
[email protected],
[email protected], [email protected],
[email protected], [email protected],
Randy Dunlap <[email protected]>,
Tyler Hicks <[email protected]>
Subject: Re: [PATCH v2] treewide: Fix common grammar mistake "the the"
Date: Thu, 11 Apr 2024 22:23:45 +0200 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
Le 11/04/2024 à 19:11, Thorsten Blum a écrit :
> Use `find . -type f -exec sed -i 's/\<the the\>/the/g' {} +` to find all
> occurrences of "the the" and replace them with a single "the".
>
> In arch/arm/include/asm/unwind.h replace "the the" with "to the".
>
> Changes only comments and documentation - no code changes.
>
> Signed-off-by: Thorsten Blum <[email protected]>
> Reviewed-by: Randy Dunlap <[email protected]>
> Reviewed-by: Tyler Hicks <[email protected]>
...
> --- a/drivers/scsi/isci/host.h
> +++ b/drivers/scsi/isci/host.h
> @@ -244,7 +244,7 @@ enum sci_controller_states {
> SCIC_INITIALIZED,
>
> /**
> - * This state indicates the the controller is in the process of becoming
maybe: that the?
> + * This state indicates the controller is in the process of becoming
> * ready (i.e. starting). In this state no new IO operations are permitted.
> * This state is entered from the INITIALIZED state.
> */
...
> diff --git a/io_uring/kbuf.c b/io_uring/kbuf.c
> index 3aa16e27f509..503244e8470a 100644
> --- a/io_uring/kbuf.c
> +++ b/io_uring/kbuf.c
> @@ -731,7 +731,7 @@ struct io_buffer_list *io_pbuf_get_bl(struct io_ring_ctx *ctx,
> * going away, if someone is trying to be sneaky. Look it up under rcu
> * so we know it's not going away, and attempt to grab a reference to
> * it. If the ref is already zero, then fail the mapping. If successful,
> - * the caller will call io_put_bl() to drop the the reference at at the
> + * the caller will call io_put_bl() to drop the reference at at the
Not strictly related to your patch, but "at at".
> * end. This may then safely free the buffer_list (and drop the pages)
> * at that point, vm_insert_pages() would've already grabbed the
> * necessary vma references.
...
CJ
prev parent reply other threads:[~2024-04-11 20:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 15:04 [PATCH] treewide: Fix common grammar mistake "the the" Thorsten Blum
2024-04-11 15:13 ` Randy Dunlap
2024-04-11 15:25 ` Dan Carpenter
2024-04-11 22:39 ` Thorsten Blum
2024-04-12 6:41 ` Jani Nikula
2024-04-11 15:37 ` Johannes Berg
2024-04-11 16:29 ` Tyler Hicks
2024-04-11 16:45 ` Robin Murphy
2024-04-11 17:11 ` [PATCH v2] " Thorsten Blum
2024-04-11 20:23 ` Christophe JAILLET [this message]
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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