[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPcyv4iYP-7QtO7hDkAeaxJsfUCrCTBSJi3bK6e5v-VVAKQz-w@mail.gmail.com>
Date: Mon, 17 Jun 2019 14:09:24 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: Christoph Hellwig <hch@....de>
Cc: Jérôme Glisse <jglisse@...hat.com>,
Jason Gunthorpe <jgg@...lanox.com>,
Ben Skeggs <bskeggs@...hat.com>, Linux MM <linux-mm@...ck.org>,
nouveau@...ts.freedesktop.org,
Maling list - DRI developers
<dri-devel@...ts.freedesktop.org>,
linux-nvdimm <linux-nvdimm@...ts.01.org>,
linux-pci@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Logan Gunthorpe <logang@...tatee.com>
Subject: Re: [PATCH 08/25] memremap: move dev_pagemap callbacks into a
separate structure
On Mon, Jun 17, 2019 at 12:59 PM Christoph Hellwig <hch@....de> wrote:
>
> On Mon, Jun 17, 2019 at 10:51:35AM -0700, Dan Williams wrote:
> > > - struct dev_pagemap *pgmap = _pgmap;
> >
> > Whoops, needed to keep this line to avoid:
> >
> > tools/testing/nvdimm/test/iomap.c:109:11: error: ‘pgmap’ undeclared
> > (first use in this function); did you mean ‘_pgmap’?
>
> So I really shouldn't be tripping over this anymore, but can we somehow
> this mess?
>
> - at least add it to the normal build system and kconfig deps instead
> of stashing it away so that things like buildbot can build it?
> - at least allow building it (under COMPILE_TEST) if needed even when
> pmem.ko and friends are built in the kernel?
Done: https://patchwork.kernel.org/patch/11000477/
Powered by blists - more mailing lists