From: Nikolay Borisov <nborisov@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v3 2/2] btrfs: Hook btrfs' DRW lock to locktorture infrastructure
Date: Mon, 24 Feb 2020 17:32:48 +0200 [thread overview]
Message-ID: <56a96841-d39f-bb9d-c8dc-c04e96087a95@suse.com> (raw)
In-Reply-To: <20200224152637.30774-3-nborisov@suse.com>
On 24.02.20 г. 17:26 ч., Nikolay Borisov wrote:
> Signed-off-by: Nikolay Borisov <nborisov@suse.com>
Ignore this one and instead replace it with the Implement DRW locking
that I just sent ...
next prev parent reply other threads:[~2020-02-24 15:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 15:26 [PATCH v3 0/2] Refactor snapshot vs nocow writers locking Nikolay Borisov
2020-02-24 15:26 ` [PATCH v3 1/2] btrfs: convert snapshot/nocow exlcusion to drw lock Nikolay Borisov
2020-02-24 15:26 ` [PATCH v3 2/2] btrfs: Hook btrfs' DRW lock to locktorture infrastructure Nikolay Borisov
2020-02-24 15:32 ` Nikolay Borisov [this message]
2020-02-24 15:32 ` [PATCH 1/2] btrfs: Implement DRW lock Nikolay Borisov
2020-02-24 16:02 ` [PATCH v3 0/2] Refactor snapshot vs nocow writers locking 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=56a96841-d39f-bb9d-c8dc-c04e96087a95@suse.com \
--to=nborisov@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