From: Jeff Layton <jlayton@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Ilya Dryomov <idryomov@gmail.com>,
ceph-devel@vger.kernel.org
Subject: Re: [PATCH] ceph: ceph_features.h: drop duplicated word in a comment
Date: Sat, 18 Jul 2020 07:00:06 -0400 [thread overview]
Message-ID: <db5f0447a43c9820a020d1dfcb80637029e4e516.camel@kernel.org> (raw)
In-Reply-To: <37c50064-e4ee-d79f-5a9f-2824479b01ca@infradead.org>
On Fri, 2020-07-17 at 16:36 -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: Ilya Dryomov <idryomov@gmail.com>
> Cc: Jeff Layton <jlayton@kernel.org>
> Cc: ceph-devel@vger.kernel.org
> ---
> include/linux/ceph/ceph_features.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- linux-next-20200714.orig/include/linux/ceph/ceph_features.h
> +++ linux-next-20200714/include/linux/ceph/ceph_features.h
> @@ -58,7 +58,7 @@
> * because 10.2.z (jewel) did not care if its peers advertised this
> * feature bit.
> *
> - * - In the second phase we stop advertising the the bit and call it
> + * - In the second phase we stop advertising the bit and call it
> * RETIRED. This can normally be done in the *next* major release
> * following the one in which we marked the feature DEPRECATED. In
> * the above example, for 12.0.z (luminous) we can say:
>
Merged into the testing branch. Thanks, Randy!
--
Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2020-07-18 11:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 23:36 Randy Dunlap
2020-07-18 11:00 ` Jeff Layton [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=db5f0447a43c9820a020d1dfcb80637029e4e516.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome