From: David Sterba <dsterba@suse.cz>
To: Andrea Gelmini <andrea.gelmini@gelma.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Fix typos
Date: Wed, 28 Nov 2018 16:56:20 +0100 [thread overview]
Message-ID: <20181128155619.GS2842@twin.jikos.cz> (raw)
In-Reply-To: <20181128110513.6079-1-andrea.gelmini@gelma.net>
On Wed, Nov 28, 2018 at 12:05:13PM +0100, Andrea Gelmini wrote:
> Signed-off-by: Andrea Gelmini <andrea.gelmini@gelma.net>
> ---
>
> Stupid fixes. Made on 4.20-rc4, and ported on linux-next (next-20181128).
Thanks, such patches are accepted once in a while when the amount of new
typo fixes becomes noticeable.
> fs/btrfs/backref.c | 4 ++--
> fs/btrfs/check-integrity.c | 2 +-
> fs/btrfs/compression.c | 4 ++--
> fs/btrfs/ctree.c | 4 ++--
> fs/btrfs/dev-replace.c | 2 +-
> fs/btrfs/disk-io.c | 4 ++--
> fs/btrfs/extent-tree.c | 28 ++++++++++++++--------------
> fs/btrfs/extent_io.c | 4 ++--
> fs/btrfs/extent_io.h | 2 +-
> fs/btrfs/extent_map.c | 2 +-
> fs/btrfs/file.c | 6 +++---
> fs/btrfs/free-space-tree.c | 2 +-
> fs/btrfs/inode.c | 10 +++++-----
> fs/btrfs/ioctl.c | 4 ++--
> fs/btrfs/lzo.c | 2 +-
> fs/btrfs/qgroup.c | 14 +++++++-------
> fs/btrfs/qgroup.h | 4 ++--
> fs/btrfs/raid56.c | 2 +-
> fs/btrfs/ref-verify.c | 6 +++---
> fs/btrfs/relocation.c | 2 +-
> fs/btrfs/scrub.c | 2 +-
> fs/btrfs/send.c | 4 ++--
> fs/btrfs/super.c | 8 ++++----
> fs/btrfs/transaction.c | 4 ++--
> fs/btrfs/tree-checker.c | 6 +++---
> fs/btrfs/tree-log.c | 4 ++--
> fs/btrfs/volumes.c | 8 ++++----
> 27 files changed, 72 insertions(+), 72 deletions(-)
Approves.
> @@ -1010,14 +1010,14 @@ int btrfs_lookup_extent_info(struct btrfs_trans_handle *trans,
> *
> * - multiple snapshots, subvolumes, or different generations in one subvol
> * - different files inside a single subvolume
> - * - different offsets inside a file (bookend extents in file.c)
> + * - different offsets inside a file (booked extents in file.c)
> *
> * The extent ref structure for the implicit back refs has fields for:
> *
> * - Objectid of the subvolume root
> * - objectid of the file holding the reference
> * - original offset in the file
> - * - how many bookend extents
> + * - how many booked extents
Please note that 'bookend' is not a typo here. The meaning used for
btrfs is close to 2a or 2b in https://www.merriam-webster.com/dictionary/bookend
and refers to the mechanism how blocks are shared by extents and
lengthier explanation would show why snapshots are so cheap (I really
tried to write a tl;dr version, but nope).
next prev parent reply other threads:[~2018-11-28 15:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 11:05 [PATCH] Fix typos Andrea Gelmini
2018-11-28 11:23 ` Nikolay Borisov
2018-11-28 13:24 ` Brendan Hide
2018-11-28 13:41 ` Nikolay Borisov
2018-11-28 15:56 ` David Sterba [this message]
2018-11-28 16:17 ` Andrea Gelmini
2018-11-28 17:02 ` David Sterba
2018-11-28 17:12 ` Andrea Gelmini
2018-12-13 21:59 ` David Sterba
2018-12-29 15:29 ` Andrea Gelmini
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=20181128155619.GS2842@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=andrea.gelmini@gelma.net \
--cc=linux-btrfs@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 NNTP newsgroup(s).