From: David Sterba <dsterba@suse.com>
To: Anand Jain <anand.jain@oracle.com>
Cc: dsterba@suse.com, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/6] sysfs-part2 Add seed device representation on the sysfs
Date: Thu, 6 Aug 2015 14:31:14 +0200 [thread overview]
Message-ID: <20150806123114.GJ31669@suse.cz> (raw)
In-Reply-To: <55C28554.708@oracle.com>
On Thu, Aug 06, 2015 at 05:51:16AM +0800, Anand Jain wrote:
...
> these can go in.
>
> >> Btrfs: sysfs: support seed devices in the sysfs layout
> >
> > Sorry for late reply, the patches look good. I'm going to prepare a
> > branch for pull into 4.3. Thanks.
>
> I suggested if this can wait.
> on the 2nd thought, I am preparing to conduct a survey to know most
> preferred sysfs layout for btrfs.
> mainly between
> one, less invasive overlays on the existing layout (current method).
> the other, separates FS and Volume attributes (old method).
>
> sorry that I am going back a bit, but i think its worth as these API
> are forever.
Understood.
prev parent reply other threads:[~2015-08-06 12:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 7:32 [PATCH 0/6] sysfs-part2 Add seed device representation on the sysfs Anand Jain
2015-07-08 7:32 ` [PATCH 1/6] Btrfs: rename btrfs_sysfs_add_one to btrfs_sysfs_add_mounted Anand Jain
2015-07-08 7:32 ` [PATCH 2/6] Btrfs: rename btrfs_sysfs_remove_one to btrfs_sysfs_remove_mounted Anand Jain
2015-07-08 7:32 ` [PATCH 3/6] Btrfs: rename btrfs_kobj_add_device to btrfs_sysfs_add_device_link Anand Jain
2015-07-08 7:32 ` [PATCH 4/6] Btrfs: rename btrfs_kobj_rm_device to btrfs_sysfs_rm_device_link Anand Jain
2015-07-08 7:32 ` [PATCH 5/6] Btrfs: rename super_kobj to fsid_kobj Anand Jain
2015-07-08 7:32 ` [PATCH 6/6] Btrfs: sysfs: support seed devices in the sysfs layout Anand Jain
2015-08-05 17:29 ` [PATCH 0/6] sysfs-part2 Add seed device representation on the sysfs David Sterba
2015-08-05 21:51 ` Anand Jain
2015-08-06 12:31 ` David Sterba [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=20150806123114.GJ31669@suse.cz \
--to=dsterba@suse.com \
--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;
as well as URLs for NNTP newsgroup(s).