From: Karim Yaghmour <karim@opersys.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
LTT-Dev <ltt-dev@shafik.org>
Subject: Re: [PATCH 2/8 ] ltt for 2.6.10 : core headers
Date: Fri, 14 Jan 2005 16:54:12 -0500 [thread overview]
Message-ID: <41E83F84.7080102@opersys.com> (raw)
In-Reply-To: <20050114205507.GD8385@mars.ravnborg.org>
Hello Sam,
Sam Ravnborg wrote:
> include/linux/*.h is supposed to include only definitions used by other
> parts of the kernel.
> Definitions used only internally by ltt shall stay in kernel/
>
> This is generally agreed upon, but not yet common practice.
Should there be a kernel/ltt-core.h or should I just put all required
definitions in kernel/ltt-core.c? The latter would result in a
cluttered C file, I think. Though there aren't any .h's in kernel/,
so I'm not sure what's the best way to proceed here.
> Btw. did you run it through sparse?
> Not that I found something, but did not see sparse annotation at first
> sight.
No I haven't. I've added it to my to-do list.
Karim
--
Author, Speaker, Developer, Consultant
Pushing Embedded and Real-Time Linux Systems Beyond the Limits
http://www.opersys.com || karim@opersys.com || 1-866-677-4546
next prev parent reply other threads:[~2005-01-14 21:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-14 6:11 [PATCH 2/8 ] ltt for 2.6.10 : core headers Karim Yaghmour
2005-01-14 20:55 ` Sam Ravnborg
2005-01-14 21:54 ` Karim Yaghmour [this message]
2005-01-14 22:48 ` Sam Ravnborg
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=41E83F84.7080102@opersys.com \
--to=karim@opersys.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@shafik.org \
--cc=sam@ravnborg.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