From: John Garry <john.garry@huawei.com>
To: Johannes Thumshirn <jthumshirn@suse.de>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>,
Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>,
Linux SCSI Mailinglist <linux-scsi@vger.kernel.org>,
Hannes Reinecke <hare@suse.de>,
James Bottomley <jejb@linux.vnet.ibm.com>,
Jinpu Wang <jinpu.wang@profitbricks.com>,
Linuxarm <linuxarm@huawei.com>
Subject: Re: [PATCH] scsi: sas: move scsi_remove_host call into sas_remove_host
Date: Mon, 24 Apr 2017 11:09:03 +0100 [thread overview]
Message-ID: <c3ddfbfd-1b4f-d53b-d9b3-9d475985ce9e@huawei.com> (raw)
In-Reply-To: <20170421121141.20701-1-jthumshirn@suse.de>
On 21/04/2017 13:11, Johannes Thumshirn wrote:
> Move scsi_remove_host call into sas_remove_host and remove it from SAS HBA
> drivers, so we don't mess up the ordering. This solves an issue with double
> deleting sysfs entries that was introduced by the change of sysfs behaviour
> from commit bcdde7e ("sysfs: make __sysfs_remove_dir() recursive").
>
> Signed-off-by: Johannes Thumshirn <jthumshirn@suse.de>
> Suggested-by: Christoph Hellwig <hch@lst.de>
> Cc: Hannes Reinecke <hare@suse.de>
> Cc: James Bottomley <jejb@linux.vnet.ibm.com>
> Cc: Jinpu Wang <jinpu.wang@profitbricks.com>
> Cc: John Garry <john.garry@huawei.com>
For what it's worth:
Tested-by: John Garry <john.garry@huawei.com> # On hisi_sas
next prev parent reply other threads:[~2017-04-24 10:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 12:11 Johannes Thumshirn
2017-04-21 12:49 ` Christoph Hellwig
2017-04-21 13:00 ` Jinpu Wang
2017-04-21 14:37 ` Martin K. Petersen
2017-04-24 9:14 ` Hannes Reinecke
2017-04-24 10:09 ` John Garry [this message]
2017-04-24 13:38 ` John Garry
2017-04-24 13:52 ` 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=c3ddfbfd-1b4f-d53b-d9b3-9d475985ce9e@huawei.com \
--to=john.garry@huawei.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=jinpu.wang@profitbricks.com \
--cc=jthumshirn@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--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
all inboxes | Powered by JetHome®