From: Michal Hocko <mhocko@kernel.org>
To: Tobias Klauser <tklauser@distanz.ch>
Cc: Arnd Bergmann <arnd@arndb.de>,
Andrew Morton <akpm@linux-foundation.org>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
Ley Foon Tan <lftan@altera.com>
Subject: Re: [PATCH] asm-generic/io.h: remove unnecessary #include of <linux/vmalloc.h>
Date: Tue, 9 May 2017 15:40:56 +0200 [thread overview]
Message-ID: <20170509134056.GM6481@dhcp22.suse.cz> (raw)
In-Reply-To: <20170509131620.GH10395@distanz.ch>
On Tue 09-05-17 15:16:20, Tobias Klauser wrote:
> On 2017-05-09 at 11:02:07 +0200, Michal Hocko <mhocko@kernel.org> wrote:
> > On Tue 09-05-17 10:50:45, Tobias Klauser wrote:
> > > After commit 1f5307b1e094 ("mm, vmalloc: properly track vmalloc users")
> > > the build for ARCH=nios2 fails with:
> > >
> > > In file included from ./include/asm-generic/io.h:767:0,
> > > from ./arch/nios2/include/asm/io.h:61,
> > > from ./include/linux/io.h:25,
> > > from ./arch/nios2/include/asm/pgtable.h:18,
> > > from ./include/linux/mm.h:70,
> > > from ./include/linux/pid_namespace.h:6,
> > > from ./include/linux/ptrace.h:9,
> > > from ./arch/nios2/include/uapi/asm/elf.h:23,
> > > from ./arch/nios2/include/asm/elf.h:22,
> > > from ./include/linux/elf.h:4,
> > > from ./include/linux/module.h:15,
> > > from init/main.c:16:
> > > ./include/linux/vmalloc.h: In function '__vmalloc_node_flags':
> > > ./include/linux/vmalloc.h:99:40: error: 'PAGE_KERNEL' undeclared (first use in this function); did you mean 'GFP_KERNEL'?
> > >
> > > which is due to the newly added #include <asm/pgtable.h>, which on nios2
> > > includes <linux/io.h> and thus <asm/io.h> and <asm-generic/io.h> which
> > > again includes <linux/vmalloc.h>.
> > >
> > > It turns out the #include <linux/vmalloc.h> in <asm-generic/io.h> isn't
> > > necessary at all since none of it definitions are used there, so remove
> > > it alltogether.
> >
> > Thanks for your fix but I have already posted a different one [1] which
> > doesn't include pgtable.h because this turned out to be a problem on
> > m68k already. I am just waiting for Andrew to drop the previous patch
> > and replace it with the one pointed out.
> >
> > [1] http://lkml.kernel.org/r/20170503063750.GC1236@dhcp22.suse.cz
>
> Thanks for the info. Though it looks like your original patch already
> made it into Linus' tree as commit 1f5307b1e094.
Ups! I though Andrew would leave it for later as it had compilation
issues.
> As for my patch, please disregard - it lead to several build regressions
> with the kernel build bot.
Yeah, I've learned that as well, so I've rather came with a different
solution. I will poke Andrew to marge a fix ASAP.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2017-05-09 13:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 8:50 [PATCH] asm-generic/io.h: remove unnecessary #include of <linux/vmalloc.h> Tobias Klauser
2017-05-09 9:02 ` Michal Hocko
2017-05-09 13:16 ` Tobias Klauser
2017-05-09 13:40 ` Michal Hocko [this message]
2017-05-09 13:40 ` Michal Hocko
2017-05-09 12:01 ` kbuild test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170509134056.GM6481@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=lftan@altera.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tklauser@distanz.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).