From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: some questions about generated headers
Date: Sat, 9 Feb 2008 20:48:53 +0100 [thread overview]
Message-ID: <200802092048.54168.bzolnier@gmail.com> (raw)
In-Reply-To: <alpine.LFD.1.00.0802091345150.14859@localhost.localdomain>
On Saturday 09 February 2008, Robert P. J. Day wrote:
[...]
>> 3)
>
> related to 2), what's up with __KERNEL as well? it still shows up
> in a number of places in the kernel source. for example, see
> include/linux/hdsmart.h:
>
> ...
> #ifndef __KERNEL
> ...
> #endif /* __KERNEL__ *
>
> (and that missing trailing slash creeps me out, too.)
These hdsmart.h goofups are my doings. 8)
[ I must have been half-asleep while making these changes but no harm
for kernel side was done (this file is not used by kernel anymore)
and yes, I didn't have motivation to look up for answer to 3) so I've
just put fdefs there. ]
Thanks,
Bart
prev parent reply other threads:[~2008-02-09 19:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-09 19:07 some questions about generated headers Robert P. J. Day
2008-02-09 19:48 ` Bartlomiej Zolnierkiewicz [this message]
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=200802092048.54168.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
/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