From: David Sterba <dsterba@suse.cz>
To: Anand Jain <anand.jain@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 1/5] btrfs: fix comment its device list mutex not volume lock
Date: Mon, 11 Feb 2019 19:41:07 +0100 [thread overview]
Message-ID: <20190211184107.GY2900@twin.jikos.cz> (raw)
In-Reply-To: <1549611577-15478-1-git-send-email-anand.jain@oracle.com>
On Fri, Feb 08, 2019 at 03:39:37PM +0800, Anand Jain wrote:
> We have killed volume mutex (commit: dccdb07bc996
> btrfs: kill btrfs_fs_info::volume_mutex). This a trival one seems to have
> escaped.
>
> Signed-off-by: Anand Jain <anand.jain@oracle.com>
> ---
> v2: Delete the wrong comment instead of fixing it.
This patch has been added to misc-next, thanks.
next prev parent reply other threads:[~2019-02-11 18:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 7:02 [PATCH 0/5] Misc props.c cleanups Anand Jain
2019-02-08 7:02 ` [PATCH 1/5] btrfs: fix comment its device list mutex not volume lock Anand Jain
2019-02-08 7:07 ` Nikolay Borisov
2019-02-08 7:16 ` Anand Jain
2019-02-08 7:19 ` Nikolay Borisov
2019-02-08 7:39 ` [PATCH v2 " Anand Jain
2019-02-11 18:41 ` David Sterba [this message]
2019-02-08 7:02 ` [PATCH 2/5] btrfs: kill __btrfs_set_prop() Anand Jain
2019-02-08 7:02 ` [PATCH 3/5] btrfs: reorg functions to drop forward declaration Anand Jain
2019-02-08 7:10 ` Nikolay Borisov
2019-02-11 18:43 ` David Sterba
2019-02-08 7:02 ` [PATCH 4/5] btrfs: drop redundant forward declaration in props.c Anand Jain
2019-02-08 7:09 ` Nikolay Borisov
2019-02-08 7:02 ` [PATCH 5/5] btrfs: trivial, fix c coding style Anand Jain
2019-02-08 7:09 ` Nikolay Borisov
2019-02-08 7:15 ` [PATCH 0/5] Misc props.c cleanups Nikolay Borisov
2019-02-08 7:31 ` 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=20190211184107.GY2900@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=anand.jain@oracle.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