mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Viacheslav Dubeyko <slava@dubeyko.com>
To: Ryusuke Konishi <konishi.ryusuke@gmail.com>,
	Hemanth Selam <hemanth.selam@gmail.com>
Cc: linux-nilfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nilfs2: fix typos in comments
Date: Mon, 07 Sep 2026 10:17:56 -0700	[thread overview]
Message-ID: <8f5f256ff990d747edbed26240e8e9ffdfe8ea83.camel@dubeyko.com> (raw)
In-Reply-To: <CAKFNMok3MaD+fRcG6VbBRND3gZa+APt_jV63KtQzXzpX6vdCCw@mail.gmail.com>

On Mon, 2026-09-07 at 17:26 +0900, Ryusuke Konishi wrote:
> On Mon, Sep 7, 2026 at 3:24 PM Hemanth Selam wrote:
> > 
> > Fix typos in comments, reported by scripts/checkpatch.pl using the
> > misspelling list in scripts/spelling.txt.  Only touches comments,
> > no code
> > changes.
> > 
> > Assisted-by: Cursor:claude-opus-5
> > Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>
> > ---
> 
> Acked-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>
> 
> Hemanth Selam, thank you for the patch.
> 
> Viacheslav, could you please add this to the queue for the next cycle
> as well?
> 
> Thanks,
> Ryusuke Konishi
> 
> >  fs/nilfs2/sufile.c | 2 +-
> >  fs/nilfs2/super.c  | 2 +-
> >  2 files changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/fs/nilfs2/sufile.c b/fs/nilfs2/sufile.c
> > index eceedca02697..6918be6fce2e 100644
> > --- a/fs/nilfs2/sufile.c
> > +++ b/fs/nilfs2/sufile.c
> > @@ -1050,7 +1050,7 @@ ssize_t nilfs_sufile_set_suinfo(struct inode
> > *sufile, void *buf,
> >   * len:                number of Bytes to trim from start
> >   * minlen:     minimum extent length in Bytes
> >   *
> > - * Decription: nilfs_sufile_trim_fs goes through all segments
> > containing bytes
> > + * Description: nilfs_sufile_trim_fs goes through all segments
> > containing bytes
> >   * from start to start+len. start is rounded up to the next block
> > boundary
> >   * and start+len is rounded down. For each clean segment
> > blkdev_issue_discard
> >   * function is invoked.
> > diff --git a/fs/nilfs2/super.c b/fs/nilfs2/super.c
> > index 893a504cb80c..65f44ff6779e 100644
> > --- a/fs/nilfs2/super.c
> > +++ b/fs/nilfs2/super.c
> > @@ -654,7 +654,7 @@ static int nilfs_statfs(struct dentry *dentry,
> > struct kstatfs *buf)
> >                         /*
> >                          * If nilfs_palloc_count_max_entries()
> > returns
> >                          * -ERANGE error code then we simply treat
> > -                        * curent inodes count as maximum possible
> > and
> > +                        * current inodes count as maximum possible
> > and
> >                          * zero as free inodes value.
> >                          */
> >                         nmaxinodes = atomic64_read(&root-
> > >inodes_count);
> > --
> > 2.48.1
> > 

Applied.

Thanks,
Slava.

  reply	other threads:[~2026-09-07 17:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07  6:24 Hemanth Selam
2026-09-07  8:26 ` Ryusuke Konishi
2026-09-07 17:17   ` Viacheslav Dubeyko [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-04-09  4:35 [PATCH] nilfs2: Fix " Ryusuke Konishi
2021-04-09  4:54 ` Ryusuke Konishi

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=8f5f256ff990d747edbed26240e8e9ffdfe8ea83.camel@dubeyko.com \
    --to=slava@dubeyko.com \
    --cc=hemanth.selam@gmail.com \
    --cc=konishi.ryusuke@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nilfs@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

all inboxes | Powered by JetHome®