From: Martin Wilck <mwilck@suse.de>
To: Don Brace <don.brace@microsemi.com>,
Johannes Thumshirn <jthumshirn@suse.de>
Cc: dl-esc-Team ESD Storage Dev Support
<esc-TeamESDStorageDevSupport@microsemi.com>,
"iss_storagedev@hp.com" <iss_storagedev@hp.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"JBottomley@odin.com" <JBottomley@odin.com>,
"hch@lst.de" <hch@lst.de>, "hare@suse.de" <hare@suse.de>
Subject: Re: [PATCH 2/2] hpsa: destroy sas transport properties before scsi_host
Date: Wed, 11 Oct 2017 11:15:08 +0200 [thread overview]
Message-ID: <1507713308.3223.9.camel@suse.de> (raw)
In-Reply-To: <4993A297653ECB4581FA5C3C31323D1967210680@avsrvexchmbx2.microsemi.net>
On Tue, 2017-10-10 at 23:04 +0000, Don Brace wrote:
> Now that Hannes's patch 9441284fbc39610c0f9ec0ed118ff85d78352906
> has been applied, this patch corrects the stack trace issue.
>
> Would you like to re-submit this patch or would you like me to send
> it up?
> I'll run some quick tests if you do decide to send it up.
> If you want me to send it up, you will get the credit anyway.
>From my PoV, just go ahead and re-submit. It'll be faster than me
diving into this again.
Thanks,
Martin
next prev parent reply other threads:[~2017-10-11 9:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 14:04 [PATCH 0/2] hpsa: fix rmmod issues Martin Wilck
2016-11-21 14:04 ` [PATCH 1/2] hpsa: cleanup sas_phy structures in sysfs when unloading Martin Wilck
2016-11-21 14:13 ` Johannes Thumshirn
2016-11-21 15:13 ` Martin Wilck
2016-11-22 3:47 ` Martin K. Petersen
2016-11-22 8:10 ` Johannes Thumshirn
2016-11-29 1:52 ` Don Brace
2016-11-29 9:16 ` Martin Wilck
2016-11-21 14:04 ` [PATCH 2/2] hpsa: destroy sas transport properties before scsi_host Martin Wilck
2016-11-21 14:14 ` Johannes Thumshirn
2017-10-10 23:04 ` Don Brace
2017-10-11 9:15 ` Martin Wilck [this message]
2016-12-01 23:22 ` [PATCH 0/2] hpsa: fix rmmod issues Don Brace
2016-12-02 8:58 ` Martin Wilck
2016-12-02 15:44 ` Don Brace
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=1507713308.3223.9.camel@suse.de \
--to=mwilck@suse.de \
--cc=JBottomley@odin.com \
--cc=don.brace@microsemi.com \
--cc=esc-TeamESDStorageDevSupport@microsemi.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=iss_storagedev@hp.com \
--cc=jthumshirn@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 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).