From: Miao Xie <miaox@cn.fujitsu.com>
To: Anand Jain <anand.jain@oracle.com>, Chris Mason <clm@fb.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Btrfs: fix wrong uevent target
Date: Fri, 4 Jul 2014 12:18:42 +0800 [thread overview]
Message-ID: <53B62B22.3060404@cn.fujitsu.com> (raw)
In-Reply-To: <53B5939B.2050808@oracle.com>
On Fri, 4 Jul 2014 01:32:11 +0800, Anand Jain wrote:
> Chris,
>
> This fix is theoretically correct but my guess that this would
> solve problem as reported by Qu Wenruo was wrong [1].
> Patch is good to integrate.
>
> Thanks, Anand
>
> [1] Re: [PATCH RFC] btrfs: Add ctime/mtime update for btrfs device add/remove.
I have merged this patch(just change the changelog) and other important bug fix patches
into my tree to make it easier to be merged into Chris's for-linus branch. The URL is
https://github.com/miaoxie/linux-btrfs.git for-3.16-rcX
But because there are some old patches in the current for-linus branch, if someone want to
merge my branch to for-linus, he/she must reset for-linus branch to
commit 2aa06a35d06a34b3109bdbf1d653de1695dc8f12
Author: Eric Sandeen <sandeen@redhat.com>
Date: Fri Jun 27 16:50:31 2014 -0500
btrfs: fix nossd and ssd_spread mount option regression
then can pull my branch and merge it into for-linus branch directly.
Thanks
Miao
> On 03/07/2014 22:00, Chris Mason wrote:
>> On 07/03/2014 07:09 AM, Miao Xie wrote:
>>> CC Anand Jain
>>>
>>> Sorry, please ignore this patch.
>>> Anand wrote the same patch several days ago, so this bug fix belongs to Anand
>>> though he NACKed his patch at that time.
>>
>> It certainly looks right, but Anand had mentioned that he had a few
>> questions on testing. I've pulled it out for now, but I'll take Anand's
>> version when you're both happy.
>>
>> -chris
>
prev parent reply other threads:[~2014-07-04 4:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 9:03 [PATCH] Btrfs: fix wrong uevent target Miao Xie
2014-07-03 11:09 ` Miao Xie
2014-07-03 14:00 ` Chris Mason
2014-07-03 17:32 ` Anand Jain
2014-07-04 1:58 ` Qu Wenruo
2014-07-04 4:18 ` Miao Xie [this message]
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=53B62B22.3060404@cn.fujitsu.com \
--to=miaox@cn.fujitsu.com \
--cc=anand.jain@oracle.com \
--cc=clm@fb.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 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.