From: Jes Sorensen <jes@wildopensource.com>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: Matthew Wilcox <willy@debian.org>,
Daniel Stekloff <dsteklof@us.ibm.com>,
Christoph Hellwig <hch@infradead.org>,
linux-hotplug-devel@lists.sourceforge.net,
linux-scsi@vger.kernel.org
Subject: Re: [announce] scsi_id 0.1 - generate unique scsi id
Date: 23 Oct 2003 03:33:32 -0400 [thread overview]
Message-ID: <yq04qy0be7n.fsf@wildopensource.com> (raw)
In-Reply-To: <20031022091519.A11995@beaverton.ibm.com>
>>>>> "Patrick" == Patrick Mansfield <patmans@us.ibm.com> writes:
Patrick> On Wed, Oct 22, 2003 at 04:52:31PM +0100, Matthew Wilcox
Patrick> wrote:
>> You shouldn't be installing them into the <sys/> namespace, that's
>> basically owned by POSIX. How about <sysfs/> instead?
Patrick> I incorrectly suggested we should use <sys/>.
Patrick> Should we use <linux/>, rather than another new directory?
Rule of thumb: any existing hierachy is reserved, either you want to
drop it in header root, ie. /usr/include or /usr/loca/include or you
want to create your own hierachy, <sysfs/> as Matthew suggested looks
like a good candidate to me.
Cheers,
Jes
next prev parent reply other threads:[~2003-10-23 7:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 23:58 [announce] scsi_id 0.1 - generate unique scsi id Patrick Mansfield
2003-10-22 14:31 ` Christoph Hellwig
2003-10-22 7:42 ` Daniel Stekloff
2003-10-22 14:46 ` Christoph Hellwig
2003-10-22 8:05 ` Daniel Stekloff
2003-10-22 15:52 ` Matthew Wilcox
2003-10-22 16:15 ` Patrick Mansfield
2003-10-22 16:23 ` Christoph Hellwig
2003-10-23 7:33 ` Jes Sorensen [this message]
2003-10-24 21:33 ` Steven Dake
2003-10-27 14:16 ` Philip R. Auld
2003-10-27 15:27 ` Patrick Mansfield
2003-10-27 17:06 ` Philip R. Auld
2003-10-27 17:31 ` Patrick Mansfield
2003-10-28 14:19 ` Philip R. Auld
2003-10-28 15:06 ` Patrick Mansfield
2003-10-28 15:40 ` Philip R. Auld
2003-10-28 16:29 ` Patrick Mansfield
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=yq04qy0be7n.fsf@wildopensource.com \
--to=jes@wildopensource.com \
--cc=dsteklof@us.ibm.com \
--cc=hch@infradead.org \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-scsi@vger.kernel.org \
--cc=patmans@us.ibm.com \
--cc=willy@debian.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