All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Daniel Vacek <neelx@suse.com>
Cc: Hemanth Selam <hemanth.selam@gmail.com>, Chris Mason <clm@fb.com>,
	David Sterba <dsterba@suse.com>,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] btrfs: fix typos and repeated words in comments
Date: Mon, 7 Sep 2026 11:22:47 +0200	[thread overview]
Message-ID: <20260907092247.GP9053@suse.cz> (raw)
In-Reply-To: <CAPjX3FfQ4X4Bd-1-_Q3h4azLM98vnJLfZ8TvduPK6zf=y==Z2g@mail.gmail.com>

On Mon, Sep 07, 2026 at 11:15:33AM +0200, Daniel Vacek wrote:
> > --- a/fs/btrfs/raid56.c
> > +++ b/fs/btrfs/raid56.c
> > @@ -953,7 +953,7 @@ static void rbio_orig_end_io(struct btrfs_raid_bio *rbio, blk_status_t status)
> >
> >         /*
> >          * Clear the data bitmap, as the rbio may be cached for later usage.
> > -        * do this before before unlock_stripe() so there will be no new bio
> > +        * do this before unlock_stripe() so there will be no new bio
> >          * for this bio.
> 
> The sentence should start with a capital. Perhaps it would also fit
> into two lines?

Reformatting whole lines makes the typos harder to spot, so it's fine to
leave it like that and reformat at commit time eventually.

  reply	other threads:[~2026-09-07  9:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07  4:48 [PATCH v2] btrfs: fix typos and repeated words in comments Hemanth Selam
2026-09-07  9:15 ` Daniel Vacek
2026-09-07  9:22   ` David Sterba [this message]
2026-09-07  9:58     ` Daniel Vacek
2026-09-07 10:06 ` David Sterba

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=20260907092247.GP9053@suse.cz \
    --to=dsterba@suse.cz \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=hemanth.selam@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neelx@suse.com \
    /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.