From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xfs: Rudimentary spelling fix
Date: Mon, 22 Mar 2021 09:16:09 +0530 [thread overview]
Message-ID: <YFgTAcZrVwPGgWEM@ArchLinux> (raw)
In-Reply-To: <20210322033316.GB22100@magnolia>
[-- Attachment #1: Type: text/plain, Size: 1059 bytes --]
On 20:33 Sun 21 Mar 2021, Darrick J. Wong wrote:
>On Sun, Mar 21, 2021 at 07:52:41PM -0700, Randy Dunlap wrote:
>> On 3/21/21 7:46 PM, Bhaskar Chowdhury wrote:
>> >
>> > s/sytemcall/systemcall/
>> >
>> >
>> > Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
>> > ---
>> > fs/xfs/xfs_inode.c | 2 +-
>> > 1 file changed, 1 insertion(+), 1 deletion(-)
>> >
>> > diff --git a/fs/xfs/xfs_inode.c b/fs/xfs/xfs_inode.c
>> > index f93370bd7b1e..b5eef9f09c00 100644
>> > --- a/fs/xfs/xfs_inode.c
>> > +++ b/fs/xfs/xfs_inode.c
>> > @@ -2870,7 +2870,7 @@ xfs_finish_rename(
>> > /*
>> > * xfs_cross_rename()
>> > *
>> > - * responsible for handling RENAME_EXCHANGE flag in renameat2() sytemcall
>> > + * responsible for handling RENAME_EXCHANGE flag in renameat2() systemcall
>> > */
>> > STATIC int
>> > xfs_cross_rename(
>> > --
>>
>> I'll leave it up to Darrick or someone else.
>>
>> To me it's "syscall" or "system call".
>
>Agreed; could you change it to one of Randy's suggestions, please?
>
Sent out a V2. pls check.
>--D
>
>> --
>> ~Randy
>>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-03-22 3:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 2:46 [PATCH] xfs: Rudimentary spelling fix Bhaskar Chowdhury
2021-03-22 2:52 ` Randy Dunlap
2021-03-22 3:33 ` Darrick J. Wong
2021-03-22 3:46 ` Bhaskar Chowdhury [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=YFgTAcZrVwPGgWEM@ArchLinux \
--to=unixbhaskar@gmail.com \
--cc=djwong@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@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.