All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org, dsterba@suse.com
Cc: l@damenly.su
Subject: [PATCH V5 0/2] btrfs: device_list_mutex fix lockdep warn and cleanup
Date: Tue, 31 Aug 2021 09:21:27 +0800	[thread overview]
Message-ID: <cover.1630370459.git.anand.jain@oracle.com> (raw)

There are no new patches here. These patches were once independent and or
part of another set in the mainline list. But now, as these two patches
are related, so they are brought together in this set.

These two patches were at V2 and V4 (respectively) at their last reroll.
Here I have marked them both to be at V5 to avoid any confusion. But
there is no code change.

Patch 1/2 is an old patch in the mailing list, now part of this set as a
new cleanup patch 2/2 depends on it.

Patch 2/2 was sent before as part of the patchset (btrf_show_devname
related fixes). And, now in this set as it depends on 1/2.

Anand Jain (2):
  btrfs: fix lockdep warning while mounting sprout fs
  btrfs: consolidate device_list_mutex in prepare_sprout to its parent

 fs/btrfs/volumes.c | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

-- 
2.31.1


             reply	other threads:[~2021-08-31  1:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-31  1:21 Anand Jain [this message]
2021-08-31  1:21 ` [PATCH V5 1/2] btrfs: fix lockdep warning while mounting sprout fs Anand Jain
2021-08-31  8:18   ` Nikolay Borisov
2021-09-02 23:51     ` Anand Jain
2021-08-31 12:37   ` Nikolay Borisov
2021-09-01  0:49   ` Su Yue
2021-09-02 15:28   ` David Sterba
2021-08-31  1:21 ` [PATCH RFC V5 2/2] btrfs: consolidate device_list_mutex in prepare_sprout to its parent Anand Jain
2021-08-31 13:03   ` Nikolay Borisov
2021-09-03  3:08     ` Anand Jain
2021-09-17 15:37   ` David Sterba
2021-09-18  0:10     ` Anand Jain

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=cover.1630370459.git.anand.jain@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=dsterba@suse.com \
    --cc=l@damenly.su \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.