From: Jeff Layton <jlayton@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Cc: Ilya Dryomov <idryomov@gmail.com>, ceph-devel@vger.kernel.org
Subject: Re: [PATCH] ceph: super.h: delete a duplicated word
Date: Thu, 23 Jul 2020 13:22:56 -0400 [thread overview]
Message-ID: <cba36614f44285feca178f1936fec8d1eef4b8ac.camel@kernel.org> (raw)
In-Reply-To: <20200720001259.21668-1-rdunlap@infradead.org>
On Sun, 2020-07-19 at 17:12 -0700, Randy Dunlap wrote:
> Drop the repeated word "the" in a comment.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Jeff Layton <jlayton@kernel.org>
> Cc: Ilya Dryomov <idryomov@gmail.com>
> Cc: ceph-devel@vger.kernel.org
> ---
> fs/ceph/super.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- linux-next-20200717.orig/fs/ceph/super.h
> +++ linux-next-20200717/fs/ceph/super.h
> @@ -353,7 +353,7 @@ struct ceph_inode_info {
> unsigned i_dirty_caps, i_flushing_caps; /* mask of dirtied fields */
>
> /*
> - * Link to the the auth cap's session's s_cap_dirty list. s_cap_dirty
> + * Link to the auth cap's session's s_cap_dirty list. s_cap_dirty
> * is protected by the mdsc->cap_dirty_lock, but each individual item
> * is also protected by the inode's i_ceph_lock. Walking s_cap_dirty
> * requires the mdsc->cap_dirty_lock. List presence for an item can
Thanks, merged into testing branch. If you have more of these, then it
might be good to bundle them up into a fs/ceph-wide patch. There is no
shortage of grammatical errors in fs/ceph so there could be a lot of
these.
--
Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2020-07-23 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 0:12 [PATCH] ceph: super.h: delete a duplicated word Randy Dunlap
2020-07-23 17:22 ` 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=cba36614f44285feca178f1936fec8d1eef4b8ac.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 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.