From: Daniel Phillips <phillips@arcor.de>
To: Mark Spencer <markster@linux-support.net>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Zaptel Pseudo TDM Bus
Date: Mon, 22 Jul 2002 01:09:03 +0200 [thread overview]
Message-ID: <E17WPp2-0007iI-00@starship> (raw)
In-Reply-To: <Pine.LNX.4.33.0207211551350.25617-100000@hoochie.linux-support.net>
On Sunday 21 July 2002 23:00, Mark Spencer wrote:
> > See the other poster's comment about providing a clear separation of
> > kernel and userspace components in your source tree. It just makes it
> > easier to get oriented.
>
> *nods* Actually the kernel and user packages are in different projects
> (zaptel is the kernel level interface, with only a couple of user tools
> for its configuration, while zapata is the library interface). Perhaps
> some people might want to contact me off-list to suggest cleaner ways of
> organizing the code.
I'll stay on-list just in case, it's better to have feedback.
I think you want to take everything that belongs in the kernel and put it
under a subdirectory, say, "kernel", and lay it out exactly as it would be if
your patch were accepted into linus's tree. That is, the headers go in
kernel/include/linux, the modules in kernel/drivers/asterisk/whichever.
It nests your tree more deeply, but it's going to end up like that anyway
(you hope) so it might as well be that way now.
--
Daniel
next prev parent reply other threads:[~2002-07-21 23:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-20 23:25 Mark Spencer
2002-07-21 0:52 ` Daniel Phillips
2002-07-21 18:59 ` Mark Spencer
2002-07-21 20:46 ` Daniel Phillips
2002-07-21 21:00 ` Mark Spencer
2002-07-21 21:39 ` Karim Yaghmour
2002-07-21 23:09 ` Daniel Phillips [this message]
2002-07-21 1:27 ` Daniel Phillips
2002-07-21 19:01 ` Mark Spencer
2002-07-21 20:04 ` Daniel Phillips
2002-07-21 20:49 ` Mark Spencer
2002-07-21 13:14 ` Francois Romieu
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=E17WPp2-0007iI-00@starship \
--to=phillips@arcor.de \
--cc=linux-kernel@vger.kernel.org \
--cc=markster@linux-support.net \
/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
all inboxes | Powered by JetHome®