From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] Revert "nvme: create 'slaves' and 'holders' entries for hidden controllers"
Date: Wed, 7 Mar 2018 18:18:05 +0100 [thread overview]
Message-ID: <20180307171805.GA810@lst.de> (raw)
In-Reply-To: <CALjAwxgLXdk1hhmtb3Dp2=U_o1E-MqObBxUroAj+sJU2uNHx4g@mail.gmail.com>
On Wed, Mar 07, 2018@03:56:36PM +0000, Sitsofe Wheeler wrote:
> The problem is that it's the first of its kind in regard to virtual
> slaves/devices and many of the consumers of block device sysfs simply
> weren't ready for it to appear where it did. Perhaps if it had been a
> different part of sysfs hierarchy and/or linked up a different way
> (virtual-slaves/?) it would have been invisible to programs that
> weren't ready to consume it...
Yes, I think we should simply creates a paths/ directory. Not sure
there is much point in the backlink.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Sitsofe Wheeler <sitsofe@gmail.com>
Cc: Keith Busch <keith.busch@intel.com>,
Hannes Reinecke <hare@suse.de>, Christoph Hellwig <hch@lst.de>,
linux-nvme@lists.infradead.org, Jens Axboe <axboe@kernel.dk>,
sagi@grimberg.me, Potnuri Bharat Teja <bharat@chelsio.com>,
Karel Zak <kzak@redhat.com>, stable <stable@vger.kernel.org>
Subject: Re: [PATCH] Revert "nvme: create 'slaves' and 'holders' entries for hidden controllers"
Date: Wed, 7 Mar 2018 18:18:05 +0100 [thread overview]
Message-ID: <20180307171805.GA810@lst.de> (raw)
In-Reply-To: <CALjAwxgLXdk1hhmtb3Dp2=U_o1E-MqObBxUroAj+sJU2uNHx4g@mail.gmail.com>
On Wed, Mar 07, 2018 at 03:56:36PM +0000, Sitsofe Wheeler wrote:
> The problem is that it's the first of its kind in regard to virtual
> slaves/devices and many of the consumers of block device sysfs simply
> weren't ready for it to appear where it did. Perhaps if it had been a
> different part of sysfs hierarchy and/or linked up a different way
> (virtual-slaves/?) it would have been invisible to programs that
> weren't ready to consume it...
Yes, I think we should simply creates a paths/ directory. Not sure
there is much point in the backlink.
next prev parent reply other threads:[~2018-03-07 17:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 13:13 [PATCH] Revert "nvme: create 'slaves' and 'holders' entries for hidden controllers" Christoph Hellwig
2018-03-07 13:13 ` Christoph Hellwig
2018-03-07 13:40 ` Hannes Reinecke
2018-03-07 13:40 ` Hannes Reinecke
2018-03-07 15:03 ` Keith Busch
2018-03-07 15:03 ` Keith Busch
2018-03-07 15:56 ` Sitsofe Wheeler
2018-03-07 15:56 ` Sitsofe Wheeler
2018-03-07 17:18 ` Christoph Hellwig [this message]
2018-03-07 17:18 ` Christoph Hellwig
2018-03-07 17:38 ` Keith Busch
2018-03-07 17:38 ` Keith Busch
2018-03-07 17:47 ` Sitsofe Wheeler
2018-03-07 17:47 ` Sitsofe Wheeler
2018-03-07 20:37 ` Keith Busch
2018-03-07 20:37 ` Keith Busch
2018-03-07 21:42 ` Sitsofe Wheeler
2018-03-07 21:42 ` Sitsofe Wheeler
2018-03-08 17:14 ` Sagi Grimberg
2018-03-08 17:14 ` Sagi Grimberg
2018-03-08 22:45 ` Keith Busch
2018-03-08 22:45 ` Keith Busch
2018-03-09 8:51 ` Johannes Thumshirn
2018-03-09 8:51 ` Johannes Thumshirn
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=20180307171805.GA810@lst.de \
--to=hch@lst.de \
/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.