From: Christoph Hellwig <hch@infradead.org>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Al Viro <viro@zeniv.linux.org.uk>, Chris Mason <clm@fb.com>,
jbacik@fb.com, linux-fsdevel@vger.kernel.org,
linux-btrfs@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jeff Mahoney <jeffm@suse.com>,
fdmanana@suse.com
Subject: Re: [RFC v2 0/2] vfs / btrfs: add support for ustat()
Date: Thu, 14 Aug 2014 23:28:56 -0700 [thread overview]
Message-ID: <20140815062856.GA27487@infradead.org> (raw)
In-Reply-To: <CAB=NE6WaQqp52MfZfjcShAUchj-1B+ZMsF1r6HabSiUxFLb7jQ@mail.gmail.com>
On Thu, Aug 14, 2014 at 10:48:05PM -0400, Luis R. Rodriguez wrote:
> Any further advice? I'll submit a v3 for RFC with some small change
> for a fix for stress testing identified by Filipe Manana.
The advice is to stop setting different dev_t values for different
files in btrfs.
prev parent reply other threads:[~2014-08-15 6:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 21:37 [RFC v2 0/2] vfs / btrfs: add support for ustat() Luis R. Rodriguez
2014-07-16 21:37 ` [RFC v2 1/2] fs/super.c: add new super block sub devices super_block_dev Luis R. Rodriguez
2014-07-16 21:37 ` [RFC v2 2/2] btrfs: use the new VFS super_block_dev Luis R. Rodriguez
2014-07-17 8:03 ` [RFC v2 0/2] vfs / btrfs: add support for ustat() Christoph Hellwig
2014-07-17 17:49 ` Luis R. Rodriguez
2014-08-15 2:48 ` Luis R. Rodriguez
2014-08-15 6:28 ` Christoph Hellwig [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=20140815062856.GA27487@infradead.org \
--to=hch@infradead.org \
--cc=clm@fb.com \
--cc=fdmanana@suse.com \
--cc=jbacik@fb.com \
--cc=jeffm@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=viro@zeniv.linux.org.uk \
/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).