From: Randy Dunlap <rdunlap@infradead.org>
To: linux-fsdevel@vger.kernel.org
Cc: Alexey Dobriyan <adobriyan@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] procfs: delete duplicated words + other fixes
Date: Tue, 13 Oct 2020 22:27:22 -0700 [thread overview]
Message-ID: <8e01420e-397b-4abf-c31d-fd103cb690de@infradead.org> (raw)
In-Reply-To: <20200805024915.12231-1-rdunlap@infradead.org>
ping.
On 8/4/20 7:49 PM, Randy Dunlap wrote:
> Delete repeated words in fs/proc/.
> {the, which}
> where "which which" was changed to "with which".
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> To: linux-fsdevel@vger.kernel.org
> Cc: Alexey Dobriyan <adobriyan@gmail.com>
> Cc: linux-kernel@vger.kernel.org
> ---
> fs/proc/base.c | 2 +-
> fs/proc/proc_net.c | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> --- linux-next-20200804.orig/fs/proc/base.c
> +++ linux-next-20200804/fs/proc/base.c
> @@ -2016,7 +2016,7 @@ const struct dentry_operations pid_dentr
> * file type from dcache entry.
> *
> * Since all of the proc inode numbers are dynamically generated, the inode
> - * numbers do not exist until the inode is cache. This means creating the
> + * numbers do not exist until the inode is cache. This means creating
> * the dcache entry in readdir is necessary to keep the inode numbers
> * reported by readdir in sync with the inode numbers reported
> * by stat.
> --- linux-next-20200804.orig/fs/proc/proc_net.c
> +++ linux-next-20200804/fs/proc/proc_net.c
> @@ -140,7 +140,7 @@ EXPORT_SYMBOL_GPL(proc_create_net_data);
> * @mode: The file's access mode.
> * @parent: The parent directory in which to create.
> * @ops: The seq_file ops with which to read the file.
> - * @write: The write method which which to 'modify' the file.
> + * @write: The write method with which to 'modify' the file.
> * @data: Data for retrieval by PDE_DATA().
> *
> * Create a network namespaced proc file in the @parent directory with the
> @@ -232,7 +232,7 @@ EXPORT_SYMBOL_GPL(proc_create_net_single
> * @mode: The file's access mode.
> * @parent: The parent directory in which to create.
> * @show: The seqfile show method with which to read the file.
> - * @write: The write method which which to 'modify' the file.
> + * @write: The write method with which to 'modify' the file.
> * @data: Data for retrieval by PDE_DATA().
> *
> * Create a network-namespaced proc file in the @parent directory with the
>
--
~Randy
next prev parent reply other threads:[~2020-10-14 9:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 2:49 [PATCH] procfs: delete duplicated words + other fixes Randy Dunlap
2020-10-14 5:27 ` Randy Dunlap [this message]
2020-10-28 19:15 Randy Dunlap
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=8e01420e-397b-4abf-c31d-fd103cb690de@infradead.org \
--to=rdunlap@infradead.org \
--cc=adobriyan@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).