On Fri, Jul 29, 2016 at 09:44:02PM -0700, Dan Williams wrote:
> Currently the build fails if --enable-destructive is specified without
> --enable-test, but --enable-destructive assumes that --enable-test is
> already specified. Just force --enable-test to satisfy the requirement.
>
> Reported-by:
Currently the build fails if --enable-destructive is specified without
--enable-test, but --enable-destructive assumes that --enable-test is
already specified. Just force --enable-test to satisfy the requirement.
Reported-by: Ross Zwisler
Signed-off-by: Dan Williams
---
configure.ac | 14 +++
On Fri, Jul 29, 2016 at 3:02 PM, Ross Zwisler
wrote:
> This commit:
>
> commit 0d119368385a ("ndctl: reorganize file structure, use per sub-directory
> makefiles")
>
> reorganized the file structure & makefiles in ndctl, but broke builds that
> used the --enable-destructive option. Here are some
On Fri, Jul 29, 2016 at 5:12 PM, Dave Chinner wrote:
> On Fri, Jul 29, 2016 at 07:44:25AM -0700, Dan Williams wrote:
>> On Thu, Jul 28, 2016 at 7:21 PM, Dave Chinner wrote:
>> > On Thu, Jul 28, 2016 at 10:10:33AM +0200, Jan Kara wrote:
>> >> On Thu 28-07-16 08:19:49, Dave Chinner wrote:
>> [..]
>
On Fri, Jul 29, 2016 at 07:44:25AM -0700, Dan Williams wrote:
> On Thu, Jul 28, 2016 at 7:21 PM, Dave Chinner wrote:
> > On Thu, Jul 28, 2016 at 10:10:33AM +0200, Jan Kara wrote:
> >> On Thu 28-07-16 08:19:49, Dave Chinner wrote:
> [..]
> >> So DAX doesn't need flushing to maintain consistent view
This commit:
commit 0d119368385a ("ndctl: reorganize file structure, use per sub-directory
makefiles")
reorganized the file structure & makefiles in ndctl, but broke builds that
used the --enable-destructive option. Here are some of the failure
messages:
../test/blk_namespaces.o: In function
On 07/29/2016 12:23 PM, Ross Zwisler wrote:
The functionality for block device DAX was already removed with this
commit:
commit acc93d30d7d4 ("Revert "block: enable dax for raw block devices"")
However, we still had a config option hanging around that was always
disabled because it depended on
The "NVDIMM Block Window Driver Writer's Guide":
http://pmem.io/documents/
http://pmem.io/documents/NVDIMM_DriverWritersGuide-July-2016.pdf
defines the layout of the block window status register. For the July 2016
version of the spec linked to above, this happens in Figure 4 on page 26.
The onl
On Fri, Jul 29, 2016 at 11:23 AM, Ross Zwisler
wrote:
> The functionality for block device DAX was already removed with this
> commit:
>
> commit acc93d30d7d4 ("Revert "block: enable dax for raw block devices"")
>
> However, we still had a config option hanging around that was always
> disabled be
The functionality for block device DAX was already removed with this
commit:
commit acc93d30d7d4 ("Revert "block: enable dax for raw block devices"")
However, we still had a config option hanging around that was always
disabled because it depended on CONFIG_BROKEN. This config option was
introdu
On Thu, Jul 28, 2016 at 7:21 PM, Dave Chinner wrote:
> On Thu, Jul 28, 2016 at 10:10:33AM +0200, Jan Kara wrote:
>> On Thu 28-07-16 08:19:49, Dave Chinner wrote:
[..]
>> So DAX doesn't need flushing to maintain consistent view of the data but it
>> does need flushing to make sure fsync(2) results
On Thu, Jul 28, 2016 at 01:43:17PM -0400, Linda Knippers wrote:
[...]
> > +acpi_nfit_decode_dsm_mask_from_hpe2(unsigned long dsm_mask)
> > +{
> > + unsigned long cmd_mask = 0;
> > +
> > + if (test_bit(1, &dsm_mask))
> > + set_bit(ND_CMD_SMART, &dsm_mask);
> > + if (test_bit(2, &ds
12 matches
Mail list logo
