On Sat, Apr 18, 2015 at 1:07 AM, Greg KH wrote:
> On Fri, Apr 17, 2015 at 09:35:46PM -0400, Dan Williams wrote:
>> This is the position (device topology) independent method to find all
>> the NFIT-defined buses in the system. The expectation is that there
>> will only ever be one "nd" bus
On Fri, Apr 17, 2015 at 09:35:46PM -0400, Dan Williams wrote:
> This is the position (device topology) independent method to find all
> the NFIT-defined buses in the system. The expectation is that there
> will only ever be one "nd" bus discovered via /sys/class/nd/ndctl0.
> However, we allow for
On Sat, Apr 18, 2015 at 1:07 AM, Greg KH gre...@linuxfoundation.org wrote:
On Fri, Apr 17, 2015 at 09:35:46PM -0400, Dan Williams wrote:
This is the position (device topology) independent method to find all
the NFIT-defined buses in the system. The expectation is that there
will only ever be
On Fri, Apr 17, 2015 at 09:35:46PM -0400, Dan Williams wrote:
This is the position (device topology) independent method to find all
the NFIT-defined buses in the system. The expectation is that there
will only ever be one nd bus discovered via /sys/class/nd/ndctl0.
However, we allow for the
This is the position (device topology) independent method to find all
the NFIT-defined buses in the system. The expectation is that there
will only ever be one "nd" bus discovered via /sys/class/nd/ndctl0.
However, we allow for the possibility of multiple buses and they will
listed in discovery
This is the position (device topology) independent method to find all
the NFIT-defined buses in the system. The expectation is that there
will only ever be one nd bus discovered via /sys/class/nd/ndctl0.
However, we allow for the possibility of multiple buses and they will
listed in discovery
6 matches
Mail list logo