From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Chris Mason <clm@fb.com>, linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: integration tree updated
Date: Fri, 25 Jul 2014 10:16:53 +0800 [thread overview]
Message-ID: <53D1BE15.1080000@cn.fujitsu.com> (raw)
In-Reply-To: <53D1B595.7070908@fb.com>
Hi chris,
It seems that two of my wrong patches got merged in integration branch:
6068d17c8ab5bce946e9678ed2064e9f966cbe62 btrfs: Merge default subvolume
mount codes into btrfs_mount_subvol().
8a2166332e332541f13b34b7248c0f14f575731e btrfs: Call mount_subtree()
even 'subvolid=' mount option is given.
These two patches does not completely work, and the successor patch is
under review.(the show_path one)
If it is OK for you, please remove these two patches.
Thanks,
Qu
-------- Original Message --------
Subject: integration tree updated
From: Chris Mason <clm@fb.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Date: 2014年07月25日 09:40
> Hi everyone,
>
> I've pushed out my current integration branch. It does have a few of
> Miao Xie's patches missing because there were some rejects. I think
> this was just because some things got pulled in out of order, and I'll
> get it fixed up.
>
> Also missing is Mark's quota snapshot deletion fixes. They were
> crashing during btrfs/011 with CONFIG_DEBUG_PAGE_ALLOC on. We'll get
> that nailed down.
>
> integration is subject to rebasing, so please treat it more like a patch
> queue. It is very lightly tested, the goal is just to show which
> patches are already applied and which ones are still pending.
>
> Thanks!
>
> -chris
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-07-25 2:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 1:40 integration tree updated Chris Mason
2014-07-25 2:16 ` Qu Wenruo [this message]
2014-07-25 11:47 ` Chris Mason
2014-08-01 9:05 ` Anand Jain
2014-08-05 1:17 ` Chris Mason
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=53D1BE15.1080000@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).