From: Christoph Hellwig <hch@infradead.org>
To: Brian King <brking@us.ibm.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] Hidden scsi devices
Date: Thu, 22 Jan 2004 15:50:41 +0000 [thread overview]
Message-ID: <20040122155040.A12452@infradead.org> (raw)
In-Reply-To: <400FEA73.80109@us.ibm.com>; from brking@us.ibm.com on Thu, Jan 22, 2004 at 09:21:23AM -0600
Ok. Although I'd maybe write it a bit more compact, and a bit commentary
could't hurt.
/*
* Sort out hidden devices early. All real probing is done in the
* individual ->probe routines
*/
static int scsi_bus_match(struct device *dev, struct device_driver *gendrv)
{
struct scsi_device *sdev = to_scsi_device(dev);
return (sdev->hidden ? 0 : 1);
}
next prev parent reply other threads:[~2004-01-22 15:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 15:21 [PATCH] Hidden scsi devices Brian King
2004-01-22 15:50 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-22 15:57 Martin Peschke3
2004-01-22 17:07 ` Brian King
2004-01-22 17:22 ` James Bottomley
2004-01-22 17:33 ` Brian King
2004-01-22 17:50 ` James Bottomley
2004-01-22 18:42 ` Mike Anderson
2004-01-22 19:43 ` Mike Anderson
2004-01-22 19:46 ` James Bottomley
2004-01-22 20:13 ` Brian King
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=20040122155040.A12452@infradead.org \
--to=hch@infradead.org \
--cc=brking@us.ibm.com \
--cc=linux-scsi@vger.kernel.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