On Fri, Apr 08, 2005 at 01:10:11AM -0700, Jeremy Higdon wrote: > Just as a sanity check, you meant "lsscsi" and not "lssci" in your original > reply, right? Yes. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- [PATCH] Use proper seq_file api for /proc/scsi/scsi
- From: Hannes Reinecke <[email protected]>
- Re: [PATCH] Use proper seq_file api for /proc/scsi/scsi
- From: Christoph Hellwig <[email protected]>
- Re: [PATCH] Use proper seq_file api for /proc/scsi/scsi
- From: Hannes Reinecke <[email protected]>
- Re: [PATCH] Use proper seq_file api for /proc/scsi/scsi
- From: Christoph Hellwig <[email protected]>
- Re: [PATCH] Use proper seq_file api for /proc/scsi/scsi
- From: Jeremy Higdon <[email protected]>
- Re: [PATCH] Use proper seq_file api for /proc/scsi/scsi
- From: Christoph Hellwig <[email protected]>
- Re: [PATCH] Use proper seq_file api for /proc/scsi/scsi
- From: Jeremy Higdon <[email protected]>
- [PATCH] Use proper seq_file api for /proc/scsi/scsi
- Prev by Date: Re: Kernel SCM saga..
- Next by Date: [PATCH 2.6.12-rc2]: ppc32: Fix a problem with NTP on !(chrp||gemini)
- Previous by thread: Re: [PATCH] Use proper seq_file api for /proc/scsi/scsi
- Next by thread: 2.6.12-rc2 in_atomic() picks up preempt_disable()
- Index(es):
 |