All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wedgwood <cw@f00f.org>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	David Woodhouse <dwmw2@infradead.org>,
	Christoph Hellwig <hch@caldera.de>,
	Gunther Mayer <Gunther.Mayer@t-online.de>,
	paul@paulbristow.net, linux-kernel@vger.kernel.org,
	torvalds@transmeta.com
Subject: Re: (patch-2.4.6) Fix oops with Iomega Clik! (ide-floppy)
Date: Sun, 15 Jul 2001 15:56:28 +1200	[thread overview]
Message-ID: <20010715155628.F7624@weta.f00f.org> (raw)
In-Reply-To: <E15LTIY-0001Ul-00@the-village.bc.nu> <20010715154008.B7624@weta.f00f.org> <3B511226.B48B22F1@mandrakesoft.com>
In-Reply-To: <3B511226.B48B22F1@mandrakesoft.com>

On Sat, Jul 14, 2001 at 11:46:46PM -0400, Jeff Garzik wrote:

    1) this is the same fscking thing we have now with ifdef __KERNEL__

Except it is completely ignored by the preprocessor.

    2) if you are coming up with a -new- token, realize that
       kernel-private stuff is the common case, and use
       LIBC_KERNEL_SHARED_{BEGIN,END} instead

Sure, whatever works... the points I am trying to make are:

  * Don't pollute kernel headers with unnecessary pre-processor junk.

  * Give the LIBC people the power to choose which parts of the
    headers they ingore and otherwise.

  * Linus et al, can merge patches from LIBC people knowing they
    should only affect LIBC, not the kernel.


It doesn't matter what the token(s) is/are --- by making them comments
and invisible to the kernel is make life easier.

Also, if the LIBC people want something like:

        typedef unsigned int uint32_t;

then it could look like:

        /* LIBC_ONLY_BEGIN

        typedef unsigned int uint32_t;

        LIBC_ONLY_END */


or whatever. All the libc specific stuff hidden in comments, and
shared stuff indictaed by comments.  A simple script can then produce
LIBC suitable headers from the kernel ones.




  --cw



  reply	other threads:[~2001-07-15  3:56 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-14 10:38 (patch-2.4.6) Fix oops with Iomega Clik! (ide-floppy) Gunther Mayer
2001-07-14 12:15 ` Alan Cox
2001-07-14 15:00   ` Paul Bristow
2001-07-14 14:14 ` Christoph Hellwig
2001-07-14 15:18   ` Chris Wedgwood
2001-07-14 16:41   ` David Woodhouse
2001-07-14 16:47   ` David Woodhouse
2001-07-14 16:58     ` Chris Wedgwood
2001-07-14 17:02       ` Alan Cox
2001-07-14 17:11         ` Chris Wedgwood
2001-07-14 17:29           ` Jeff Garzik
2001-07-14 17:33             ` Alan Cox
2001-07-14 17:38               ` Jeff Garzik
2001-07-14 17:44                 ` Alan Cox
2001-07-14 18:04                 ` __KERNEL__ removal Jonathan Lundell
2001-07-14 18:19                   ` Jeff Garzik
2001-07-14 18:30                     ` Mo McKinlay
2001-07-15 11:53                     ` Kai Henningsen
2001-07-15 13:12                       ` Chris Wedgwood
2001-07-15 14:21                       ` Horst von Brand
2001-07-16  9:16                         ` Chris Wedgwood
2001-07-14 18:12                 ` (patch-2.4.6) Fix oops with Iomega Clik! (ide-floppy) Wichert Akkerman
2001-07-15  3:40               ` Chris Wedgwood
2001-07-15  3:46                 ` Jeff Garzik
2001-07-15  3:56                   ` Chris Wedgwood [this message]
2001-07-14 18:09     ` David Woodhouse
2001-07-14 18:21       ` Jeff Garzik
2001-07-14 18:49       ` David Woodhouse
     [not found]   ` <mailman.995129400.8760.linux-kernel2news@redhat.com>
2001-07-14 18:36     ` Pete Zaitcev

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=20010715155628.F7624@weta.f00f.org \
    --to=cw@f00f.org \
    --cc=Gunther.Mayer@t-online.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dwmw2@infradead.org \
    --cc=hch@caldera.de \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@paulbristow.net \
    --cc=torvalds@transmeta.com \
    /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.