All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Daniel Jacobowitz <dan@debian.org>
Cc: Mariusz Mazur <mmazur@kernel.pl>,
	linux-kernel@vger.kernel.org, debian-glibc@lists.debian.org
Subject: Re: Userland headers available
Date: Fri, 23 Jan 2004 14:15:36 -0500	[thread overview]
Message-ID: <401172D8.8040507@nortelnetworks.com> (raw)
In-Reply-To: 20040123184755.GA2138@nevyn.them.org

Daniel Jacobowitz wrote:

 > I would really like to come up with an approach to maintain this 
interface
 > definition in the kernel source.  I'm still trying to think of a
 > way to do it without breaking compatibility or kernel builds.

The obvious way is to have the kernel headers include the userland
headers, then everything below that be wrapped in "#ifdef __KERNEL__". 
Userland then includes the normal kernel headers, but only gets the 
userland-safe ones.

This sounds too easy though--I'm sure I've missed something, but I can't 
think what....

Chris


-- 
Chris Friesen                    | MailStop: 043/33/F10
Nortel Networks                  | work: (613) 765-0557
3500 Carling Avenue              | fax:  (613) 765-2986
Nepean, ON K2H 8E9 Canada        | email: cfriesen@nortelnetworks.com


  parent reply	other threads:[~2004-01-23 19:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-23 18:07 Userland headers available Mariusz Mazur
2004-01-23 18:47 ` Daniel Jacobowitz
2004-01-23 19:04   ` Mariusz Mazur
2004-01-23 19:15   ` Chris Friesen [this message]
2004-01-23 19:39     ` Chris Friesen
2004-01-23 23:47       ` jw schultz
2004-01-24  1:38       ` H. Peter Anvin
2004-01-25 23:30         ` Daniel Jacobowitz
2004-01-26  0:09           ` H. Peter Anvin
2004-01-23 20:28   ` 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=401172D8.8040507@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.com \
    --cc=dan@debian.org \
    --cc=debian-glibc@lists.debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmazur@kernel.pl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.