From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Nick Warne <nick@linicks.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Question on Space.c
Date: Mon, 29 May 2006 12:06:11 -0600 [thread overview]
Message-ID: <20060529120611.A30398@openss7.org> (raw)
In-Reply-To: <200605291849.04769.nick@linicks.net>; from nick@linicks.net on Mon, May 29, 2006 at 06:49:04PM +0100
Nick,
On Mon, 29 May 2006, Nick Warne wrote:
> I saw Space.o being build, and seeing as it is Capitalised thought I would see
> why, and maybe a patch to make it all lower case.
...
...
> I have looked though docs and googled as to why this One File Is Like This to
> no avail? Convention?
>
Yes, convention: SVR4 had a Space.c file for defining drivers.
--brian
prev parent reply other threads:[~2006-05-29 18:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-29 17:49 Question on Space.c Nick Warne
2006-05-29 18:05 ` Jesper Juhl
2006-05-29 18:11 ` Nick Warne
2006-05-29 19:03 ` Al Viro
2006-05-29 18:06 ` Brian F. G. Bidulock [this message]
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=20060529120611.A30398@openss7.org \
--to=bidulock@openss7.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@linicks.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