linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tobias Klauser <tklauser@distanz.ch>
To: Stafford Horne <shorne@gmail.com>, Arnd Bergmann <arnd@arndb.de>
Cc: Jonas Bonn <jonas@southpole.se>,
	Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
	openrisc@lists.librecores.org, linux-arch@vger.kernel.org,
	kbuild-all@01.org, kbuild test robot <lkp@intel.com>
Subject: Re: [PATCH] openrisc: add forward declaration for struct vm_area_struct
Date: Tue, 12 Sep 2017 09:42:05 +0200	[thread overview]
Message-ID: <20170912074204.GF5028@distanz.ch> (raw)
In-Reply-To: <20170908152911.GQ2609@lianli.shorne-pla.net>

On 2017-09-08 at 17:29:11 +0200, Stafford Horne <shorne@gmail.com> wrote:
> On Fri, Sep 08, 2017 at 10:25:08AM +0200, Tobias Klauser wrote:
> > After removing linux/vmalloc.h from asm-generic/io.h, the following
> > warning occurs on openrisc:
> > 
> >    In file included from arch/openrisc/include/asm/io.h:33:0,
> >                     from include/linux/io.h:25,
> >                     from drivers/tty/serial/earlycon.c:19:
> >    arch/openrisc/include/asm/pgtable.h:424:2: warning: 'struct vm_area_struct' declared inside parameter list
> >      unsigned long address, pte_t *pte)
> >      ^
> [..]
> > @@ -414,6 +414,8 @@ static inline void pmd_set(pmd_t *pmdp, pte_t *ptep)
> >  
> >  extern pgd_t swapper_pg_dir[PTRS_PER_PGD]; /* defined in head.S */
> >  
> > +struct vm_area_struct;
> > +
> 
> Acked-by: Stafford Horne <shorne@gmail.com>
> 
> I was kind of wondering whether is better to include linux/mm_types.h or
> linux/vmalloc.h here instead of the forward declaration.  But looking at
> how other architectures do it; about half do the forward declaration, and
> half use an include.  So I guess this is fine.
> 
> I noticed you were getting a lot of these patches done for removing
> linux/vmalloc.h from asm-generic/io.h.   Do you want me to push this
> through my queue or are you planning sending them through another route?

Arnd has applied the patch removing linux/vmalloc.h from
asm-generic/io.h to his testing tree to give it a good amount of testing
before it comes anywhere near linux-next.  I'd say it's fine if you push
this through your queue as long as it hits Linus' tree before my
patch (which Arnd will submit, I suppose?).

Arnd, what would you prefer?

  reply	other threads:[~2017-09-12  7:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-05 11:27 [PATCH] asm-generic/io.h: remove unnecessary include of linux/vmalloc.h Tobias Klauser
2017-09-05 15:11 ` Arnd Bergmann
2017-09-05 15:11   ` Arnd Bergmann
2017-09-05 15:21   ` Tobias Klauser
2017-09-05 20:49     ` Arnd Bergmann
2017-11-07 10:24   ` Tobias Klauser
2017-11-07 10:24     ` Tobias Klauser
2017-09-07 19:31 ` kbuild test robot
2017-09-08  8:25   ` [PATCH] openrisc: add forward declaration for struct vm_area_struct Tobias Klauser
2017-09-08 15:29     ` Stafford Horne
2017-09-12  7:42       ` Tobias Klauser [this message]
2017-09-12 10:37         ` Stafford Horne
2017-09-12 11:16           ` Tobias Klauser
2017-09-07 19:36 ` [PATCH] asm-generic/io.h: remove unnecessary include of linux/vmalloc.h kbuild test robot
2017-09-07 19:36   ` kbuild test robot
2017-09-08  8:22   ` Tobias Klauser

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=20170912074204.GF5028@distanz.ch \
    --to=tklauser@distanz.ch \
    --cc=arnd@arndb.de \
    --cc=jonas@southpole.se \
    --cc=kbuild-all@01.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=openrisc@lists.librecores.org \
    --cc=shorne@gmail.com \
    --cc=stefan.kristiansson@saunalahti.fi \
    /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).