From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Hannes Reinecke <hare@suse.de>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/8] scsi_dh: Implement common device table handling
Date: Thu, 17 Jul 2008 12:20:59 -0500 [thread overview]
Message-ID: <1216315259.5515.38.camel@localhost.localdomain> (raw)
In-Reply-To: <20080717073804.588C518C6FD@pentland.suse.de>
On Thu, 2008-07-17 at 09:38 +0200, Hannes Reinecke wrote:
> Instead of having each and every driver implement its own
> device table scanning code we should rather implement a common
> routine and scan the device tables there.
> This allows us also to implement a general notifier chain
> callback for all device handler instead for one per handler.
This doesn't apply against linus head:
Applying scsi_dh: Implement common device table handling
error: patch failed: drivers/scsi/device_handler/scsi_dh_emc.c:412
error: drivers/scsi/device_handler/scsi_dh_emc.c: patch does not apply
error: patch failed: drivers/scsi/device_handler/scsi_dh_hp_sw.c:108
error: drivers/scsi/device_handler/scsi_dh_hp_sw.c: patch does not apply
error: patch failed: drivers/scsi/device_handler/scsi_dh_rdac.c:590
error: drivers/scsi/device_handler/scsi_dh_rdac.c: patch does not apply
It looks like a conflict with this:
commit 33af79d12e0fa25545d49e86afc67ea8ad5f2f40
Author: Chandra Seetharaman <sekharan@us.ibm.com>
Date: Wed Jul 16 17:35:08 2008 -0700
scsi_dh: Verify "dev" is a sdev before accessing it.
James
next prev parent reply other threads:[~2008-07-17 17:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 7:38 [PATCH 1/8] scsi_dh: Implement common device table handling Hannes Reinecke
2008-07-17 17:20 ` James Bottomley [this message]
2008-07-17 17:33 ` Chandra Seetharaman
2008-07-18 13:28 ` Hannes Reinecke
-- strict thread matches above, loose matches on Subject: below --
2008-07-17 23:52 [PATCH 0/8] scsi_dh update Chandra Seetharaman
2008-07-17 23:52 ` [PATCH 1/8] scsi_dh: Implement common device table handling Chandra Seetharaman
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=1216315259.5515.38.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=hare@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.