All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: dsterba@suse.cz
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2] btrfs: cleanup assigning next active device with a check
Date: Wed, 4 May 2016 07:31:55 +0800	[thread overview]
Message-ID: <572934EB.8030604@oracle.com> (raw)
In-Reply-To: <20160503174728.GM29353@twin.jikos.cz>


>>    While here can also integrate this.
>>
>>    [PATCH 1/1] btrfs: fix lock dep warning move scratch super outside of
>> chunk_mutex
>
> That one has been in for-next for some time.

There is another patch which is similarly named (sorry about that),
I see that one but not this.

---------
git log -i --author=anand.jain@oracle.com --oneline  | egrep "btrfs: fix 
lock dep"
58681ad85b9f btrfs: fix lock dep warning, move scratch dev out of 
device_list_mutex and uuid_mutex

git status
On branch for-next
Your branch is up-to-date with 'origin/for-next'.
nothing to commit, working directory clean
----------

Thanks, Anand

  reply	other threads:[~2016-05-03 23:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-18 11:25 [PATCH] btrfs: cleanup assigning next active device with a check Anand Jain
2016-04-25 15:15 ` David Sterba
2016-05-01 23:05   ` Anand Jain
2016-05-01 23:02 ` [PATCH v2] " Anand Jain
2016-05-02 15:26   ` David Sterba
2016-05-03 10:01     ` Anand Jain
2016-05-03 17:47       ` David Sterba
2016-05-03 23:31         ` Anand Jain [this message]
2016-05-04  9:00           ` David Sterba
2016-05-04  8:44         ` David Sterba
2016-05-03  9:44 ` [PATCH] " 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=572934EB.8030604@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=dsterba@suse.cz \
    --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.