From: David Sterba <dsterba@suse.cz>
To: Colin Ian King <colin.i.king@gmail.com>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] btrfs: Fix spelling mistake "decompresssed" -> "decompressed"
Date: Fri, 3 May 2024 13:41:54 +0200 [thread overview]
Message-ID: <20240503114154.GV2585@twin.jikos.cz> (raw)
In-Reply-To: <20240503094040.2712326-1-colin.i.king@gmail.com>
On Fri, May 03, 2024 at 10:40:40AM +0100, Colin Ian King wrote:
> There is a spelling mistake in a btrfs_err message. Fix it.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
Updated in the patch, thanks.
prev parent reply other threads:[~2024-05-03 11:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 9:40 [PATCH][next] btrfs: Fix spelling mistake "decompresssed" -> "decompressed" Colin Ian King
2024-05-03 11:41 ` David Sterba [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=20240503114154.GV2585@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=colin.i.king@gmail.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-btrfs@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 read-only IMAP folder(s) and NNTP newsgroup(s).