From: Chris Wedgwood <cw@f00f.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
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:40:08 +1200 [thread overview]
Message-ID: <20010715154008.B7624@weta.f00f.org> (raw)
In-Reply-To: <E15LTIY-0001Ul-00@the-village.bc.nu>
In-Reply-To: <E15LTIY-0001Ul-00@the-village.bc.nu>
On Sat, Jul 14, 2001 at 06:33:45PM +0100, Alan Cox wrote:
That just generates work for the glibc folks when they are working
off copies of kernel header snapshots as they need to
Can't we just do something like:
/* KERNEL_PRIVATE_BEGIN: blah */
struct internal organs(int foo, char *bar);
/* KERNEL_PRIVATE_END */
sort of thing? That way glibc people can use sed to eliminate bogons
and confilcts and they can also submit patches for areas of overlap
the kernel people miss --- without fear of breaking the kernel?
Seems win-win to me and stops glibc and kernel developers from having
to trip over people and will allow us to eliminate all the rediculous
numbers of __KERNEL__ checks.
--cw
next prev parent reply other threads:[~2001-07-15 3:40 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 [this message]
2001-07-15 3:46 ` Jeff Garzik
2001-07-15 3:56 ` Chris Wedgwood
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=20010715154008.B7624@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.