All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <natechancellor@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	clang-built-linux <clang-built-linux@googlegroups.com>
Subject: Re: [PATCH] clang: linux/compiler-clang.h: drop duplicated word in a comment
Date: Fri, 17 Jul 2020 19:58:23 -0700	[thread overview]
Message-ID: <20200718025823.GA1188976@ubuntu-n2-xlarge-x86> (raw)
In-Reply-To: <6a18c301-3505-742f-4dd7-0f38d0e537b9@infradead.org>

On Fri, Jul 17, 2020 at 07:55:02PM -0700, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
> 
> Drop the doubled word "the" in a comment.
> 
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: clang-built-linux@googlegroups.com

Reviewed-by: Nathan Chancellor <natechancellor@gmail.com>

> ---
>  include/linux/compiler-clang.h |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> --- linux-next-20200714.orig/include/linux/compiler-clang.h
> +++ linux-next-20200714/include/linux/compiler-clang.h
> @@ -40,7 +40,7 @@
>  #endif
>  
>  /*
> - * Not all versions of clang implement the the type-generic versions
> + * Not all versions of clang implement the type-generic versions
>   * of the builtin overflow checkers. Fortunately, clang implements
>   * __has_builtin allowing us to avoid awkward version
>   * checks. Unfortunately, we don't know which version of gcc clang
> 

      reply	other threads:[~2020-07-18  2:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-18  2:55 [PATCH] clang: linux/compiler-clang.h: drop duplicated word in a comment Randy Dunlap
2020-07-18  2:58 ` Nathan Chancellor [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 \
    --in-reply-to=20200718025823.GA1188976@ubuntu-n2-xlarge-x86 \
    --to=natechancellor@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=clang-built-linux@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.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.