From: V13 <v13@priest.com>
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Make scsi.h nominally userspace-clean
Date: Mon, 9 Aug 2004 23:48:33 +0300 [thread overview]
Message-ID: <200408092348.36583.v13@priest.com> (raw)
In-Reply-To: <20040809175200.GA28126@suse.de>
On Monday 09 August 2004 20:52, Jens Axboe wrote:
> > I do not argue that including this header file in a program is
> > appropriate, but other kernel headers already take as many precautions
> > as this patch introduces. I chose __u8 over uint8_t as more in the
> > style of the kernel generally.
> >
> > Please keep me on cc:; I do not subscribe to the lists.
>
> I already sent such a patch to Linus.
Do you accept patches like '#include <linux/compiler.h>' (for header file to
be used by userspace) or was this an exception ?
<<V13>>
next prev parent reply other threads:[~2004-08-09 20:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 17:24 [PATCH] Make scsi.h nominally userspace-clean Noah Misch
2004-08-09 17:52 ` Jens Axboe
2004-08-09 20:48 ` V13 [this message]
2004-08-09 18:26 ` James Courtier-Dutton
-- strict thread matches above, loose matches on Subject: below --
2004-08-09 17:53 Joerg Schilling
2004-08-09 17:56 ` Jens Axboe
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=200408092348.36583.v13@priest.com \
--to=v13@priest.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.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