public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: Linus Torvalds <torvalds@osdl.org>,
	rolandd@cisco.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] missing includes from infiniband merge
Date: Sun, 24 Sep 2006 08:44:47 +0200	[thread overview]
Message-ID: <20060924064446.GA13320@uranus.ravnborg.org> (raw)
In-Reply-To: <20060923203605.GN29920@ftp.linux.org.uk>

On Sat, Sep 23, 2006 at 09:36:05PM +0100, Al Viro wrote:
> > A better fix would be to avoid the arch dependency in the non-arch .h
> > files so that in most cases it just works??
> 
> What "it"?  Use of vmalloc() without including vmalloc.h since on i386
> it just happens to be pulled via the
> linux/pci.h -> linux/dmapool.h -> asm-i386/io.h -> linux/vmalloc.h
> chain?
The other way around. Try to get rid of the evil includes in arch-$(ASM)
that is just sitting there for no other purpose than to let a developer skip
a single include.
In this case the right fix IMO would have been to kill the include of
linux/vmalloc.h from asm-i386/io.h and let all users that previously failed
to include vmalloc.h now do so themself.

Looking through asm-i386/io.h at fist look there is zero use of
linux/vmalloc.h so the include has no business there.

With this your patch would obviously be needed and on top of this we would
have to fix other places that 'forget' to include vmalloc.h but the good thing
would be that this is now a bit more consistent across architectures.

	Sam

  parent reply	other threads:[~2006-09-24  6:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-23 15:44 [PATCH] missing includes from infiniband merge Al Viro
2006-09-23 17:35 ` Roland Dreier
2006-09-23 20:29 ` Sam Ravnborg
2006-09-23 20:36   ` Al Viro
2006-09-23 20:54     ` Al Viro
2006-09-24  6:44     ` Sam Ravnborg [this message]
2006-09-24 19:19       ` Al Viro
2006-09-24 20:52         ` Sam Ravnborg
2006-09-24 21:35           ` Al Viro
2006-09-24 21:56             ` Sam Ravnborg

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=20060924064446.GA13320@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rolandd@cisco.com \
    --cc=torvalds@osdl.org \
    --cc=viro@ftp.linux.org.uk \
    /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