From: Arnd Bergmann <arnd@arndb.de>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: alan@redhat.com, arjanv@redhat.com, chrisw@osdl.org,
Jan Glauber1 <jan.glauber@de.ibm.com>,
linux-390@vm.marist.edu, linux-kernel@vger.kernel.org,
mulix@mulix.org, tim.bird@am.sony.com
Subject: Re: [PATCH] cputime (3/6): move jiffies stuff to jiffies.h
Date: Fri, 6 Aug 2004 17:10:28 +0200 [thread overview]
Message-ID: <200408061710.34015.arnd@arndb.de> (raw)
In-Reply-To: <OF45879196.98545410-ON42256EE8.003A9AD5-42256EE8.003B151C@de.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 665 bytes --]
On Freitag, 6. August 2004 12:45, Martin Schwidefsky wrote:
> The times man pages says that the struct tms is defined in sys/times.h.
> This doesn't make it necessary to have a linux/times.h header file.
> These are kernel headers and not user space headers. Does anybody think
> it's important to keep the user/kernel header files names similar ?
I suppose the main point is that stuff like klibc it is better to keep
the existing obvious implementation of sys/times.h instead of changing
it to a less obvious one. Right now, all non linux specific
klibc/include/sys/foo.h files start with #include <linux/foo.h>, which
just makes sense.
Arnd <><
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next parent reply other threads:[~2004-08-06 15:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF45879196.98545410-ON42256EE8.003A9AD5-42256EE8.003B151C@de.ibm.com>
2004-08-06 15:10 ` Arnd Bergmann [this message]
2004-08-05 18:04 [PATCH] cputime (3/6): move jiffies stuff to jiffies.h Martin Schwidefsky
2004-08-05 20:40 ` Arnd Bergmann
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=200408061710.34015.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=alan@redhat.com \
--cc=arjanv@redhat.com \
--cc=chrisw@osdl.org \
--cc=jan.glauber@de.ibm.com \
--cc=linux-390@vm.marist.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mulix@mulix.org \
--cc=schwidefsky@de.ibm.com \
--cc=tim.bird@am.sony.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox