* RFC: move kernel/memremap.c to mm/
@ 2019-07-18 5:48 Christoph Hellwig
2019-07-18 6:03 ` Dan Williams
0 siblings, 1 reply; 2+ messages in thread
From: Christoph Hellwig @ 2019-07-18 5:48 UTC (permalink / raw)
To: Dan Williams; +Cc: Jason Gunthorpe, linux-mm, linux-kernel
Hi Dan,
was there any really good reason to have memremap.c in kernel/ back
when you started it? It seems to be pretty much tried into the mm
infrastructure, and I keep mistyping the path. Would you mind a simple
git-mv patch after -rc1 to move it to mm/ ?
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: RFC: move kernel/memremap.c to mm/
2019-07-18 5:48 RFC: move kernel/memremap.c to mm/ Christoph Hellwig
@ 2019-07-18 6:03 ` Dan Williams
0 siblings, 0 replies; 2+ messages in thread
From: Dan Williams @ 2019-07-18 6:03 UTC (permalink / raw)
To: Christoph Hellwig; +Cc: Jason Gunthorpe, Linux MM, Linux Kernel Mailing List
On Wed, Jul 17, 2019 at 10:49 PM Christoph Hellwig <hch@lst.de> wrote:
>
> Hi Dan,
>
> was there any really good reason to have memremap.c in kernel/ back
> when you started it? It seems to be pretty much tried into the mm
> infrastructure, and I keep mistyping the path. Would you mind a simple
> git-mv patch after -rc1 to move it to mm/ ?
No complaints from me. It ended up there because it was originally
just the common memremap implementation always built with
CONFIG_HAS_IOMEM.
Arguably we should have done this move right after commit 5981690ddb8f
("memremap: split devm_memremap_pages() and memremap()
infrastructure").
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-07-18 6:04 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-07-18 5:48 RFC: move kernel/memremap.c to mm/ Christoph Hellwig
2019-07-18 6:03 ` Dan Williams
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox