From: Christoph Hellwig <hch@infradead.org>
To: Daniel Stekloff <dsteklof@us.ibm.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Patrick Mansfield <patmans@us.ibm.com>,
linux-hotplug-devel@lists.sourceforge,
linux-scsi@vger.kernel.org
Subject: Re: [announce] scsi_id 0.1 - generate unique scsi id
Date: Wed, 22 Oct 2003 15:46:38 +0100 [thread overview]
Message-ID: <20031022154638.A22952@infradead.org> (raw)
In-Reply-To: <1066808536.27285.19.camel@w-stekloff.beaverton.ibm.com>; from dsteklof@us.ibm.com on Wed, Oct 22, 2003 at 12:42:16AM -0700
On Wed, Oct 22, 2003 at 12:42:16AM -0700, Daniel Stekloff wrote:
> > Umm, libsysfs isn't installing headers into /usr/include/sys, is it?
> > Especially with something like dlist.h that sounds like yet another
> > linked list implementation..
>
>
>
> Patrick told me about this, we will change libsysfs to install headers
> there.
??
s/there/not there/
> Is there another linked list implementation that you'd recommend?
I'd recommend not to expose your linked list implementation to
libsysfs users. If you really need it might be best to use <sys/queue.h>
although it's quite ugly. But if dlist.h is the one from evms is certainly
much much better than that one 8)
next prev parent reply other threads:[~2003-10-22 14:46 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 [this message]
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
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=20031022154638.A22952@infradead.org \
--to=hch@infradead.org \
--cc=dsteklof@us.ibm.com \
--cc=linux-hotplug-devel@lists.sourceforge \
--cc=linux-scsi@vger.kernel.org \
--cc=patmans@us.ibm.com \
/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