From: Josef Bacik <josef@toxicpanda.com>
To: David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/2] Block size helper cleanups
Date: Wed, 17 Jan 2024 13:53:02 -0500 [thread overview]
Message-ID: <20240117185302.GA4022278@perftesting> (raw)
In-Reply-To: <cover.1705511340.git.dsterba@suse.com>
On Wed, Jan 17, 2024 at 06:10:13PM +0100, David Sterba wrote:
> Unify using fs_info::sectorsize for inode or superblock.
>
> David Sterba (2):
> btrfs: replace sb::s_blocksize by fs_info::sectorsize
> btrfs: replace i_blocksize by fs_info::sectorsize
Reviewed-by: Josef Bacik <josef@toxicpanda.com>
Thanks,
Josef
next prev parent reply other threads:[~2024-01-17 18:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 17:10 [PATCH 0/2] Block size helper cleanups David Sterba
2024-01-17 17:10 ` [PATCH 1/2] btrfs: replace sb::s_blocksize by fs_info::sectorsize David Sterba
2024-01-17 17:10 ` [PATCH 2/2] btrfs: replace i_blocksize " David Sterba
2024-01-17 18:53 ` Josef Bacik [this message]
2024-01-18 6:16 ` [PATCH 0/2] Block size helper cleanups Anand Jain
2024-01-18 22:29 ` 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=20240117185302.GA4022278@perftesting \
--to=josef@toxicpanda.com \
--cc=dsterba@suse.com \
--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