mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: zhumao001@208suo.com
Cc: peterz@infradead.org, jpoimboe@kernel.org, jbaron@akamai.com,
	ardb@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Delete unneeded word in comment
Date: Tue, 20 Jun 2023 10:35:35 -0400	[thread overview]
Message-ID: <20230620103535.57f18960@gandalf.local.home> (raw)
In-Reply-To: <373dff7d57a69ec00de7e206895ddbb9@208suo.com>

On Sun, 18 Jun 2023 22:47:48 +0800
zhumao001@208suo.com wrote:


Subject needs a topic. Please read:

   https://docs.kernel.org/process/submitting-patches.html


> Delete the unneeded word 'with' in comment.
> 
> Signed-off-by: Zhu Mao <zhumao001@208suo.com>
> ---
>   kernel/jump_label.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/kernel/jump_label.c b/kernel/jump_label.c
> index d9c822bbffb8..08c42ae723ef 100644
> --- a/kernel/jump_label.c
> +++ b/kernel/jump_label.c
> @@ -493,7 +493,7 @@ void __init jump_label_init(void)
> 
>       /*
>        * Since we are initializing the static_key.enabled field with
> -     * with the 'raw' int values (to avoid pulling in atomic.h) in
> +     * the 'raw' int values (to avoid pulling in atomic.h) in

Broken whitespace.

-- Steve

>        * jump_label.h, let's make sure that is safe. There are only two
>        * cases to check since we initialize to 0 or 1.
>        */


  parent reply	other threads:[~2023-06-20 14:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230618143813.15142-1-dengshaomin@cdjrlc.com>
     [not found] ` <20230618143813.15142-4-dengshaomin@cdjrlc.com>
     [not found]   ` <610b47a2989976b9dae162ecc55ddc85@208suo.com>
2023-06-19 21:38     ` [PATCH] drm/msm: Fix typo " Dmitry Baryshkov
     [not found] ` <20230618143813.15142-2-dengshaomin@cdjrlc.com>
     [not found]   ` <373dff7d57a69ec00de7e206895ddbb9@208suo.com>
2023-06-20 14:35     ` Steven Rostedt [this message]
     [not found] ` <20230618143813.15142-3-dengshaomin@cdjrlc.com>
     [not found]   ` <0c1649d3a7eca54b639b3990c186f482@208suo.com>
2023-06-21  8:58     ` [PATCH] dma-buf: heaps: Delete repeated word Bagas Sanjaya
     [not found] ` <20230618143813.15142-6-dengshaomin@cdjrlc.com>
     [not found]   ` <aef774d1ff3b260b46d5b81f61cdccfa@208suo.com>
2023-09-21  0:14     ` [PATCH] module: Fix comment typo Luis Chamberlain

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=20230620103535.57f18960@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=ardb@kernel.org \
    --cc=jbaron@akamai.com \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=zhumao001@208suo.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

all inboxes | Powered by JetHome®