Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Josef Bacik <josef@toxicpanda.com>
To: fdmanana@kernel.org
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/6] btrfs: some tweaks and cleanups around ordered extents
Date: Tue, 4 Jun 2024 12:02:58 -0400	[thread overview]
Message-ID: <20240604160258.GE3413@localhost.localdomain> (raw)
In-Reply-To: <cover.1717495660.git.fdmanana@suse.com>

On Tue, Jun 04, 2024 at 12:08:46PM +0100, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
> 
> Details in the individual change logs.
> 

Reviewed-by: Josef Bacik <josef@toxicpanda.com>

Thanks,

Josef

  parent reply	other threads:[~2024-06-04 16:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04 11:08 [PATCH 0/6] btrfs: some tweaks and cleanups around ordered extents fdmanana
2024-06-04 11:08 ` [PATCH 1/6] btrfs: reduce critical section at btrfs_wait_ordered_roots() fdmanana
2024-06-04 11:08 ` [PATCH 2/6] btrfs: reduce critical section at btrfs_wait_ordered_extents() fdmanana
2024-06-04 11:08 ` [PATCH 3/6] btrfs: add comment about locking to btrfs_split_ordered_extent() fdmanana
2024-06-04 11:08 ` [PATCH 4/6] btrfs: avoid removal and re-insertion of split ordered extent fdmanana
2024-06-04 11:08 ` [PATCH 5/6] btrfs: mark ordered extent insertion failure checks as unlikely fdmanana
2024-06-04 11:08 ` [PATCH 6/6] btrfs: update panic message when splitting ordered extent fdmanana
2024-06-04 16:02 ` Josef Bacik [this message]
2024-06-04 22:50 ` [PATCH 0/6] btrfs: some tweaks and cleanups around ordered extents Qu Wenruo
2024-06-05  7:35 ` Johannes Thumshirn

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=20240604160258.GE3413@localhost.localdomain \
    --to=josef@toxicpanda.com \
    --cc=fdmanana@kernel.org \
    --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