From: Johannes Thumshirn <jthumshirn@suse.de>
To: James Bottomley <jejb@linux.vnet.ibm.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: Hannes Reinecke <hare@suse.de>,
Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>,
Linux SCSI Mailinglist <linux-scsi@vger.kernel.org>,
Johannes Thumshirn <jthumshirn@suse.de>
Subject: [PATCH v3 0/3] Fix panic when a SES device is attached to a hpsa logical volume.
Date: Wed, 17 Aug 2016 10:40:01 +0200 [thread overview]
Message-ID: <cover.1471423022.git.jthumshirn@suse.de> (raw)
The first patch provides stub implementations for scsi_is_sas_phy()
and sas_get_address() for the case that CONFIG_SCSI_SAS_ATTRS is not
defined.
The second patch implements the actual fix in ses.c by changing the
is_sas_attached() call to scsi_is_sas_rphy().
The third and last patch removes is_sas_attached() as it doesn't have
any more consumers left.
Changes from v2:
* Fix phy vs. rphy typo in patch 1/3.
Verified with config from http://www.spinics.net/lists/linux-scsi/msg99067.html
Johannes Thumshirn (3):
sas: provide stub implementation for scsi_is_sas_rphy
ses: use scsi_is_sas_rphy instead of is_sas_attached
sas: remove is_sas_attached()
drivers/scsi/scsi_transport_sas.c | 16 ----------------
drivers/scsi/ses.c | 2 +-
include/scsi/scsi_transport_sas.h | 5 ++---
3 files changed, 3 insertions(+), 20 deletions(-)
--
1.8.5.6
next reply other threads:[~2016-08-17 8:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 8:40 Johannes Thumshirn [this message]
2016-08-17 8:40 ` [PATCH v3 1/3] sas: provide stub implementation for scsi_is_sas_rphy Johannes Thumshirn
2016-08-17 9:19 ` kbuild test robot
2016-08-17 9:56 ` kbuild test robot
2016-08-17 8:40 ` [PATCH v3 2/3] ses: use scsi_is_sas_rphy instead of is_sas_attached Johannes Thumshirn
2016-08-17 8:40 ` [PATCH v3 3/3] sas: remove is_sas_attached() Johannes Thumshirn
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=cover.1471423022.git.jthumshirn@suse.de \
--to=jthumshirn@suse.de \
--cc=hare@suse.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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;
as well as URLs for NNTP newsgroup(s).