Delivery reports about your e-mail

˜æÔ]MiÀÃÐOžP™Ù˜„¾4ŠÓ8وŸ>®Èƒ ô‚s‘†«¤éŒÆâ܊„O9ï‘è¢ Ž´Eþ©¢Šð¦\bJ…¥ðˆî«PA¬«%þn#xF¢pŸ4h5×°v7¸SŸ¤k3]¯Ì4ß¡šFäS•ÐO“  ŒÃ/ãqǽS¹ÙSM¿%¼ºòyO 4ÚàpeNÔ® ___ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm

Re: [fstests PATCH 2/2] generic/347: dm-thin lacks DAX support

On Wed, Jan 17, 2018 at 04:23:51PM -0700, Ross Zwisler wrote: > generic/347 currently fails when run in cojunction with the DAX mount > option: > > generic/347 72s ... - output mismatch (see > /root/project/xfstests/results//generic/347.out.bad) > --- tests/generic/347.out 2016-05-12

[fstests PATCH 1/2] shared/272: don't use data journaling with DAX

shared/272 fails with kernels v4.15-rc1 and beyond when you are mounted with DAX: shared/272 [failed, exit status 1] - output mismatch (see /root/project/xfstests/results//shared/272.out.bad) --- tests/shared/272.out2015-12-05 13:12:17.038257578 -0700 +++

[fstests PATCH 2/2] generic/347: dm-thin lacks DAX support

generic/347 currently fails when run in cojunction with the DAX mount option: generic/347 72s ... - output mismatch (see /root/project/xfstests/results//generic/347.out.bad) --- tests/generic/347.out 2016-05-12 11:56:32.086618744 -0600 +++

[ndctl PATCH] ndctl, test: fix stale json in btt-pad-compat.sh

We weren't using the updated results of any but the first of the ndctl create-namespace commands. This could potentially result in the test being unreliable. Use the json being emitted by the create-namespace commands to get the device etc. for future operations. Also do a 'reset' before

Re: KVM "fake DAX" flushing interface - discussion

Hi Dan, Thanks for your reply. > > On Fri, Jan 12, 2018 at 10:23 PM, Pankaj Gupta wrote: > > > > Hello Dan, > > > >> Not a flag, but a new "Address Range Type GUID". See section "5.2.25.2 > >> System Physical Address (SPA) Range Structure" in the ACPI 6.2A > >>

Re: KVM "fake DAX" flushing interface - discussion

On Fri, Jan 12, 2018 at 10:23 PM, Pankaj Gupta wrote: > > Hello Dan, > >> Not a flag, but a new "Address Range Type GUID". See section "5.2.25.2 >> System Physical Address (SPA) Range Structure" in the ACPI 6.2A >> specification. Since it is a GUID we could define a Linux