From: Karim Yaghmour <karim@opersys.com>
To: Philippe Gerum <rpm@xenomai.org>
Cc: Pavel Machek <pavel@ucw.cz>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] I-pipe: Core implementation
Date: Mon, 20 Jun 2005 18:47:29 -0400 [thread overview]
Message-ID: <42B74781.8000109@opersys.com> (raw)
In-Reply-To: <42B7272F.2040503@xenomai.org>
Philippe Gerum wrote:
> There's a fourth one (ipipe/x86.c) added by the arch-dependent patch,
> but yes, I agree that this could sound rather overkill to have this
> support in its own dir, especially a top-level one. The files under
> ipipe/ can be built as a loadable module, hence the current layout.
> Would you see this belonging to, e.g., the driver tree instead?
How about this instead:
Arch-indepedent parts:
----------------------
include/linux/ipipe.h
kernel/ipipe/Kconfig (formerly ipipe/Kconfig)
kernel/ipipe/Makefile (formerly ipipe/Makefile)
kernel/ipipe/core.c (formerly kernel/ipipe.c)
kernel/ipipe/generic.c (formerly ipipe/generi.c)
Arch-dependent parts:
---------------------
include/asm-i386/ipipe.h
arch/i386/kernel/ipipe-core.c (formerly arch/i386/kernel/ipipe.c)
arch/i386/kernel/ipipe-root.c (formerly ipipe/x86.c)
Seems to me that the above makes more sense. Albeit you would have
parts of the module in kernel/ipipe/* and the rest in
arch/*/kernel/ipipe*.
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-06-21 2:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-17 23:21 [PATCH 1/2] I-pipe: Core implementation Philippe Gerum
2005-06-18 17:01 ` Pavel Machek
2005-06-20 20:29 ` Philippe Gerum
2005-06-20 22:47 ` Karim Yaghmour [this message]
2005-06-21 7:15 ` Philippe Gerum
2005-06-21 13:35 ` Karim Yaghmour
2005-06-21 13:56 ` Philippe Gerum
2005-06-20 20:32 ` Valdis.Kletnieks
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=42B74781.8000109@opersys.com \
--to=karim@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rpm@xenomai.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