On Tue, 2015-05-05 at 02:06 +0200, Rafael J. Wysocki wrote:
> On Tuesday, April 28, 2015 06:22:05 PM Dan Williams wrote:
> > On Tue, Apr 28, 2015 at 5:25 PM, Rafael J. Wysocki
> > wrote:
> > > On Tuesday, April 28, 2015 02:24:12 PM Dan Williams wrote:
> > >> Changes since v1 [1]: Incorporates
On Tue, 2015-05-05 at 02:06 +0200, Rafael J. Wysocki wrote:
On Tuesday, April 28, 2015 06:22:05 PM Dan Williams wrote:
On Tue, Apr 28, 2015 at 5:25 PM, Rafael J. Wysocki r...@rjwysocki.net
wrote:
On Tuesday, April 28, 2015 02:24:12 PM Dan Williams wrote:
Changes since v1 [1]:
On Tue, Apr 28, 2015 at 03:15:54PM -0700, Dan Williams wrote:
> > lsblk's blkdev_scsi_type_to_name() considers 4 to mean
> > SCSI_TYPE_WORM (write once read many ... used for certain optical
> > and tape drives).
>
> Why is lsblk assuming these are scsi devices? I'll need to go check that out.
On Tue, Apr 28, 2015 at 03:15:54PM -0700, Dan Williams wrote:
lsblk's blkdev_scsi_type_to_name() considers 4 to mean
SCSI_TYPE_WORM (write once read many ... used for certain optical
and tape drives).
Why is lsblk assuming these are scsi devices? I'll need to go check that out.
It's a
On Tuesday, April 28, 2015 06:22:05 PM Dan Williams wrote:
> On Tue, Apr 28, 2015 at 5:25 PM, Rafael J. Wysocki wrote:
> > On Tuesday, April 28, 2015 02:24:12 PM Dan Williams wrote:
> >> Changes since v1 [1]: Incorporates feedback received prior to April 24.
> >>
[cut]
> >
> > I'm wondering
On Tuesday, April 28, 2015 06:22:05 PM Dan Williams wrote:
On Tue, Apr 28, 2015 at 5:25 PM, Rafael J. Wysocki r...@rjwysocki.net wrote:
On Tuesday, April 28, 2015 02:24:12 PM Dan Williams wrote:
Changes since v1 [1]: Incorporates feedback received prior to April 24.
[cut]
I'm
On Tue, 2015-04-28 at 16:05 -0700, Andy Lutomirski wrote:
> On Tue, Apr 28, 2015 at 3:28 PM, Dan Williams
> wrote:
> > On Tue, Apr 28, 2015 at 2:06 PM, Andy Lutomirski
> > wrote:
> >> On Tue, Apr 28, 2015 at 1:59 PM, Dan Williams
> >> wrote:
> >>> On Tue, Apr 28, 2015 at 1:52 PM, Andy
On Tue, 2015-04-28 at 16:05 -0700, Andy Lutomirski wrote:
On Tue, Apr 28, 2015 at 3:28 PM, Dan Williams dan.j.willi...@intel.com
wrote:
On Tue, Apr 28, 2015 at 2:06 PM, Andy Lutomirski l...@amacapital.net
wrote:
On Tue, Apr 28, 2015 at 1:59 PM, Dan Williams dan.j.willi...@intel.com
On Tue, Apr 28, 2015 at 5:25 PM, Rafael J. Wysocki wrote:
> On Tuesday, April 28, 2015 02:24:12 PM Dan Williams wrote:
>> Changes since v1 [1]: Incorporates feedback received prior to April 24.
>>
>> 1/ Ingo said [2]:
>>
>>"So why on earth is this whole concept and the naming itself
>>
On Tuesday, April 28, 2015 02:24:12 PM Dan Williams wrote:
> Changes since v1 [1]: Incorporates feedback received prior to April 24.
>
> 1/ Ingo said [2]:
>
>"So why on earth is this whole concept and the naming itself
>('drivers/block/nd/' stands for 'NFIT Defined', apparently)
On Tue, Apr 28, 2015 at 3:28 PM, Dan Williams wrote:
> On Tue, Apr 28, 2015 at 2:06 PM, Andy Lutomirski wrote:
>> On Tue, Apr 28, 2015 at 1:59 PM, Dan Williams
>> wrote:
>>> On Tue, Apr 28, 2015 at 1:52 PM, Andy Lutomirski
>>> wrote:
On Tue, Apr 28, 2015 at 11:24 AM, Dan Williams
On Tue, Apr 28, 2015 at 2:06 PM, Andy Lutomirski wrote:
> On Tue, Apr 28, 2015 at 1:59 PM, Dan Williams
> wrote:
>> On Tue, Apr 28, 2015 at 1:52 PM, Andy Lutomirski wrote:
>>> On Tue, Apr 28, 2015 at 11:24 AM, Dan Williams
>>> wrote:
Changes since v1 [1]: Incorporates feedback received
us Torvalds
>> Subject: [Linux-nvdimm] [PATCH v2 00/20] libnd: non-volatile memory device
>> support
>>
>> Changes since v1 [1]: Incorporates feedback received prior to April 24.
>
> Here are some comments on the sysfs properties reported for a pmem device.
> They a
Wysocki; Robert Moore; Ingo Molnar; linux-a...@vger.kernel.org; Jens Axboe;
> Borislav Petkov; Thomas Gleixner; Greg KH; linux-kernel@vger.kernel.org;
> Andy Lutomirski; Andrew Morton; Linus Torvalds
> Subject: [Linux-nvdimm] [PATCH v2 00/20] libnd: non-volatile memory device
> support
>
On Tue, Apr 28, 2015 at 1:59 PM, Dan Williams wrote:
> On Tue, Apr 28, 2015 at 1:52 PM, Andy Lutomirski wrote:
>> On Tue, Apr 28, 2015 at 11:24 AM, Dan Williams
>> wrote:
>>> Changes since v1 [1]: Incorporates feedback received prior to April 24.
>>>
>>> 1/ Ingo said [2]:
>>>
>>>"So
On Tue, Apr 28, 2015 at 1:52 PM, Andy Lutomirski wrote:
> On Tue, Apr 28, 2015 at 11:24 AM, Dan Williams
> wrote:
>> Changes since v1 [1]: Incorporates feedback received prior to April 24.
>>
>> 1/ Ingo said [2]:
>>
>>"So why on earth is this whole concept and the naming itself
>>
On Tue, Apr 28, 2015 at 11:24 AM, Dan Williams wrote:
> Changes since v1 [1]: Incorporates feedback received prior to April 24.
>
> 1/ Ingo said [2]:
>
>"So why on earth is this whole concept and the naming itself
>('drivers/block/nd/' stands for 'NFIT Defined', apparently)
>
Changes since v1 [1]: Incorporates feedback received prior to April 24.
1/ Ingo said [2]:
"So why on earth is this whole concept and the naming itself
('drivers/block/nd/' stands for 'NFIT Defined', apparently)
revolving around a specific 'firmware' mindset and revolving
On Tue, Apr 28, 2015 at 3:28 PM, Dan Williams dan.j.willi...@intel.com wrote:
On Tue, Apr 28, 2015 at 2:06 PM, Andy Lutomirski l...@amacapital.net wrote:
On Tue, Apr 28, 2015 at 1:59 PM, Dan Williams dan.j.willi...@intel.com
wrote:
On Tue, Apr 28, 2015 at 1:52 PM, Andy Lutomirski
On Tue, Apr 28, 2015 at 5:25 PM, Rafael J. Wysocki r...@rjwysocki.net wrote:
On Tuesday, April 28, 2015 02:24:12 PM Dan Williams wrote:
Changes since v1 [1]: Incorporates feedback received prior to April 24.
1/ Ingo said [2]:
So why on earth is this whole concept and the naming itself
On Tuesday, April 28, 2015 02:24:12 PM Dan Williams wrote:
Changes since v1 [1]: Incorporates feedback received prior to April 24.
1/ Ingo said [2]:
So why on earth is this whole concept and the naming itself
('drivers/block/nd/' stands for 'NFIT Defined', apparently)
On Tue, Apr 28, 2015 at 1:59 PM, Dan Williams dan.j.willi...@intel.com wrote:
On Tue, Apr 28, 2015 at 1:52 PM, Andy Lutomirski l...@amacapital.net wrote:
On Tue, Apr 28, 2015 at 11:24 AM, Dan Williams dan.j.willi...@intel.com
wrote:
Changes since v1 [1]: Incorporates feedback received prior
On Tue, Apr 28, 2015 at 1:52 PM, Andy Lutomirski l...@amacapital.net wrote:
On Tue, Apr 28, 2015 at 11:24 AM, Dan Williams dan.j.willi...@intel.com
wrote:
Changes since v1 [1]: Incorporates feedback received prior to April 24.
1/ Ingo said [2]:
So why on earth is this whole concept
On Tue, Apr 28, 2015 at 2:06 PM, Andy Lutomirski l...@amacapital.net wrote:
On Tue, Apr 28, 2015 at 1:59 PM, Dan Williams dan.j.willi...@intel.com
wrote:
On Tue, Apr 28, 2015 at 1:52 PM, Andy Lutomirski l...@amacapital.net wrote:
On Tue, Apr 28, 2015 at 11:24 AM, Dan Williams
On Tue, Apr 28, 2015 at 11:24 AM, Dan Williams dan.j.willi...@intel.com wrote:
Changes since v1 [1]: Incorporates feedback received prior to April 24.
1/ Ingo said [2]:
So why on earth is this whole concept and the naming itself
('drivers/block/nd/' stands for 'NFIT Defined',
Molnar; linux-a...@vger.kernel.org; Jens Axboe;
Borislav Petkov; Thomas Gleixner; Greg KH; linux-kernel@vger.kernel.org;
Andy Lutomirski; Andrew Morton; Linus Torvalds
Subject: [Linux-nvdimm] [PATCH v2 00/20] libnd: non-volatile memory device
support
Changes since v1 [1]: Incorporates feedback
Chinner; H. Peter Anvin; Christoph Hellwig; Rafael J.
Wysocki; Robert Moore; Ingo Molnar; linux-a...@vger.kernel.org; Jens Axboe;
Borislav Petkov; Thomas Gleixner; Greg KH; linux-kernel@vger.kernel.org;
Andy Lutomirski; Andrew Morton; Linus Torvalds
Subject: [Linux-nvdimm] [PATCH v2 00/20] libnd
Changes since v1 [1]: Incorporates feedback received prior to April 24.
1/ Ingo said [2]:
So why on earth is this whole concept and the naming itself
('drivers/block/nd/' stands for 'NFIT Defined', apparently)
revolving around a specific 'firmware' mindset and revolving
28 matches
Mail list logo
