* Problems with phys_to_pfn_t in linux-next and s390
@ 2015-12-24 5:56 Guenter Roeck
2015-12-24 6:24 ` Dan Williams
0 siblings, 1 reply; 2+ messages in thread
From: Guenter Roeck @ 2015-12-24 5:56 UTC (permalink / raw)
To: Dan Williams
Cc: Andrew Morton, linux-kernel@vger.kernel.org, linux-s390,
Martin Schwidefsky
s390:defconfig:
ERROR: "phys_to_pfn_t" [drivers/s390/block/dcssblk.ko] undefined!
s390 does not set CONFIG_HAS_IOMEM, which is required for phys_to_pfn_t to exist.
Introduced with commit e014f77c4b ("mm-dax-pmem-introduce-pfn_t-v3") and
possibly earlier.
Guenter
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Problems with phys_to_pfn_t in linux-next and s390
2015-12-24 5:56 Problems with phys_to_pfn_t in linux-next and s390 Guenter Roeck
@ 2015-12-24 6:24 ` Dan Williams
0 siblings, 0 replies; 2+ messages in thread
From: Dan Williams @ 2015-12-24 6:24 UTC (permalink / raw)
To: Guenter Roeck
Cc: Andrew Morton, linux-kernel@vger.kernel.org, linux-s390,
Martin Schwidefsky
On Wed, Dec 23, 2015 at 9:56 PM, Guenter Roeck <linux@roeck-us.net> wrote:
> s390:defconfig:
>
> ERROR: "phys_to_pfn_t" [drivers/s390/block/dcssblk.ko] undefined!
>
> s390 does not set CONFIG_HAS_IOMEM, which is required for phys_to_pfn_t to
> exist.
>
> Introduced with commit e014f77c4b ("mm-dax-pmem-introduce-pfn_t-v3") and
> possibly earlier.
Addressed in v4:
https://lists.01.org/pipermail/linux-nvdimm/2015-December/003610.html
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2015-12-24 6:24 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-12-24 5:56 Problems with phys_to_pfn_t in linux-next and s390 Guenter Roeck
2015-12-24 6:24 ` Dan Williams
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox