From: Hemanth Selam <hemanth.selam@gmail.com>
To: David Sterba <dsterba@suse.com>
Cc: Daniel Vacek <neelx@suse.com>, Chris Mason <mason@kernel.org>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] btrfs: reflow comments left awkward by the typo fixes
Date: Mon, 7 Sep 2026 17:18:02 +0530 [thread overview]
Message-ID: <20260907114802.16143-1-hemanth.selam@gmail.com> (raw)
In-Reply-To: <20260907114153.39900-1-hemanth.selam@gmail.com>
Please drop this patch.
You had already answered the question it tries to address:
"Reformatting whole lines makes the typos harder to spot, so it's fine
to leave it like that and reformat at commit time eventually."
I sent it after reading Daniel's comments but before reading your reply
to them, so I reflowed the two comments you had just said not to reflow.
Entirely my fault, and easily avoided if I had read the whole thread
first. Sorry for the noise.
The typo fixes already in for-next are unaffected.
next prev parent reply other threads:[~2026-09-07 11:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 11:41 Hemanth Selam
2026-09-07 11:48 ` Hemanth Selam [this message]
2026-09-07 12:35 ` 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=20260907114802.16143-1-hemanth.selam@gmail.com \
--to=hemanth.selam@gmail.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@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 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®