From: "Ahmed S. Darwish" <darwish.07@gmail.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] ruminations on kernel.h
Date: Mon, 08 Jan 2007 02:21:58 +0000 [thread overview]
Message-ID: <20070108022158.GA17437@Ahmed> (raw)
In-Reply-To: <Pine.LNX.4.64.0701071524240.14075@localhost.localdomain>
On Sun, Jan 07, 2007 at 03:24:41PM -0500, Robert P. J. Day wrote:
>
> just thinking out loud here, but does anyone else think that the
> header file include/linux/kernel.h is a little ... unstructured?
> IMHO, i would think that it would make more sense to partition a lot
> of the content of that file into other (and possibly newer) header
> files.
>
I think so too, Kernel.h is just a collection of loosly connected maros.
Even the naming of the header relate nothing to its contents (printk Macros,
container_of, ..).
But will the community accept it easily ?. I mean this will mean patching a very
big number of files to use the new names/header files.
> thoughts? i might whip up a patch just to get some feedback.
If the community accepted it, I have some time to handle the task of patching
the files to use the new header files.
--
Ahmed S. Darwish
http://darwish-07.blogspot.com
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2007-01-08 2:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-07 20:24 [KJ] ruminations on kernel.h Robert P. J. Day
2007-01-07 20:47 ` Matthew Wilcox
2007-01-07 20:55 ` Robert P. J. Day
2007-01-07 23:18 ` Matthew Wilcox
2007-01-08 2:21 ` Ahmed S. Darwish [this message]
2007-01-08 3:07 ` Paul Bonser
2007-01-08 7:09 ` Robert P. J. Day
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=20070108022158.GA17437@Ahmed \
--to=darwish.07@gmail.com \
--cc=kernel-janitors@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 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.