public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: 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:31:40 +0100	[thread overview]
Message-ID: <20031022153140.A22298@infradead.org> (raw)
In-Reply-To: <20031021165857.A8240@beaverton.ibm.com>; from patmans@us.ibm.com on Tue, Oct 21, 2003 at 04:58:57PM -0700

On Tue, Oct 21, 2003 at 04:58:57PM -0700, Patrick Mansfield wrote:
> libsysfs 0_2_0 was not installing libsysfs.h or dlist.h, manually copy
> those files to /usr/include/sys before compiling.

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..


  reply	other threads:[~2003-10-22 14:31 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 [this message]
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
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=20031022153140.A22298@infradead.org \
    --to=hch@infradead.org \
    --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