On Thu, Nov 03, 2016 at 11:51:02AM -0600, Ross Zwisler wrote: > On Thu, Nov 03, 2016 at 12:58:26PM +1100, Dave Chinner wrote: > > On Tue, Nov 01, 2016 at 01:54:02PM -0600, Ross Zwisler wrote: > > > DAX PMDs have been disabled since Jan Kara introduced DAX radix tree based > > > locking. This series allows DAX PMDs to participate in the DAX radix tree > > > based locking scheme so that they can be re-enabled. > > > > I've seen patch 0/16 - where did you send the other 16? I need to > > pick up the bug fix that is in this patch set... > > I CC'd your "david@xxxxxxxxxxxxx" address on the entire set, as well as all > the usual lists (linux-xfs, linux-fsdevel, linux-nvdimm, etc). Ok, now I'm /really/ confused. Procmail logs show: >From ross.zwisler@xxxxxxxxxxxxxxx Wed Nov 02 06:56:46 2016 Subject: [PATCH v9 00/16] re-enable DAX PMD support Folder: incoming/xfs-linux/new/1478030206.9177_1.dastard 5348 >From ross.zwisler@xxxxxxxxxxxxxxx Wed Nov 02 06:56:48 2016 Subject: [PATCH v9 01/16] ext4: tell DAX the size of allocation holes Folder: incoming/xfs-linux/new/1478030208.9182_1.dastard 3725 >From ross.zwisler@xxxxxxxxxxxxxxx Wed Nov 02 06:56:49 2016 Subject: [PATCH v9 02/16] dax: remove buffer_size_valid() Folder: incoming/xfs-linux/new/1478030209.9187_1.dastard 4692 ..... so procmail has seen them, and put them all in the same bucket like it has for everything else. But only patch 0 appeared in my linux-xfs mail box - the rest of the files logged by procmail don't exist. No errors or indications of failures anywhere. They've just vanished into thin air... > They are also available via the libnvdimm patchwork: > > https://patchwork.kernel.org/project/linux-nvdimm/list/ > > or via my tree: > > https://git.kernel.org/cgit/linux/kernel/git/zwisler/linux.git/log/?h=dax_pmd_v9 > > The only patch that is different between v8 and v9 is: > [PATCH v9 14/16] dax: add struct iomap based DAX PMD support OK, thanks, I'll pull it in. > > > > Previously we had talked about this series going through the XFS tree, but > > > Jan has a patch set that will need to build on this series and it heavily > > > modifies the MM code. I think he would prefer that series to go through > > > Andrew Morton's -MM tree, so it probably makes sense for this series to go > > > through that same tree. > > > > Seriously, I was 10 minutes away from pushing out the previous > > version of this patchset as a stable topic branch, just like has > > been discussed and several times over the past week. Indeed, I > > mentioned that I was planning on pushing out this topic branch today > > not more than 4 hours ago, and you were on the cc list. > > I'm confused - I sent v9 of this series out 2 days ago, on Tuesday? > I have seen multiple messages from you this week saying you were going to pick > this series up, but I saw them all after I had already sent this series out. That's what I'm really confused - I replied immediately after this email appeared in my in-box - I was working from v8 because I didn't know this version existed. This v9 patch zero email hit procmail on "Wed Nov 02 06:56:46 2016" and i replied immediately when i saw it: "On Thu, Nov 03, 2016 at 12:58:26PM +1100," So there's some 30 hours between it passing through procmail and mutt adding it to my inbox. And mutt hasn't see any of the other emails in the thread. /me sighs and wonders how much other email has been going missing lately.... > Sorry for the confusion, Clearly not your fault, Ross. > I was just trying to figure out a way that Jan's > changes could also be merged. Please do pick up v9 of my PMD set. :) Will do, but I've got to find my way out of WTF-Landia first... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
