public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: Jaswinder Singh Rajput <jaswinder@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Sam Ravnborg <sam@ravnborg.org>, x86 maintainers <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL -tip v3] fix 39 'make headers_check' warnings
Date: Mon, 19 Jan 2009 12:15:52 +0100	[thread overview]
Message-ID: <20090119111552.GA18996@elte.hu> (raw)
In-Reply-To: <1232331646.5570.5.camel@brick>


* Harvey Harrison <harvey.harrison@gmail.com> wrote:

> On Mon, 2009-01-19 at 07:40 +0530, Jaswinder Singh Rajput wrote:
> > On Sun, 2009-01-18 at 19:50 +0100, Ingo Molnar wrote:
> > >  
> > > why does such a change introduce new code? It is duplicating existing code 
> > > instead of cleaning it all up.
> > > 
> > 
> > That's why I was requesting you to check asm/swab.h because I was in 
> > doubt whether we need these functions in userspace or not.
> > 
> > If we do not need these functions in userspace then I will clean these 
> > up.
> > 
> 
> As part of doing the swab.h splitout it was very tempting to just stop 
> exporting _all_ of the asm/swab.h files now that there is a 
> linux/swab.h. But I ended up leaving things as they were on arches that 
> did expose their arch specific versions to userspace.

i'd argue for a much narrower interface to user-space - we export so much 
stuff (more than 700 headers) and in such an unstructured way (75,000 
lines of code) that it's plain crazy.

So if you think no x86 userspace actually needs swab.h, we can just wrap 
it all in __KERNEL__. I guess we cannot remove swab.h from 
include/linux/Kbuild, right?

	Ingo

  reply	other threads:[~2009-01-19 11:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-18 14:04 [GIT PULL -tip v3] fix 39 'make headers_check' warnings Jaswinder Singh Rajput
2009-01-18 17:28 ` Ingo Molnar
2009-01-18 18:50   ` Ingo Molnar
2009-01-18 18:52     ` Ingo Molnar
2009-01-18 19:08     ` Sam Ravnborg
2009-01-18 19:09       ` Ingo Molnar
2009-01-18 19:45         ` Sam Ravnborg
2009-01-19  2:16       ` Jaswinder Singh Rajput
2009-01-19  5:27         ` Sam Ravnborg
2009-01-19  2:10     ` Jaswinder Singh Rajput
2009-01-19  2:20       ` Harvey Harrison
2009-01-19 11:15         ` Ingo Molnar [this message]
2009-01-19 18:08           ` Harvey Harrison
2009-01-18 18:56 ` Ingo Molnar
2009-01-19  9:19   ` Avi Kivity
2009-01-19 11:01     ` Sam Ravnborg
2009-01-19 11:53       ` Avi Kivity
2009-01-24  6:16         ` Jaswinder Singh Rajput
2009-02-04 14:28           ` Avi Kivity
2009-02-04 15:17             ` Jaswinder Singh Rajput
2009-02-04 15:40               ` Avi Kivity
2009-02-04 16:00                 ` Jaswinder Singh Rajput
2009-02-04 16:37                   ` Arnd Bergmann
2009-02-04 17:22                     ` Avi Kivity

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=20090119111552.GA18996@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=harvey.harrison@gmail.com \
    --cc=jaswinder@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=x86@kernel.org \
    /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