From: "Ewan D. Milne" <emilne@redhat.com>
To: Daniel Wagner <dwagner@suse.de>, James Smart <james.smart@broadcom.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Dick Kennedy <dick.kennedy@broadcom.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi: lpfc: Move work items to a stack list
Date: Mon, 25 Nov 2019 11:40:07 -0500 [thread overview]
Message-ID: <44cc15adc190fb1f6f89cbb8478aadda35f6b1e2.camel@redhat.com> (raw)
In-Reply-To: <20191119181435.taxa56wbf4zd4f2f@beryllium.lan>
[ removed linux-kernel from cc: ]
We may have hit the same issue in testing, we're looking at it.
-Ewan
next prev parent reply other threads:[~2019-11-25 16:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 8:08 [PATCH] scsi: lpfc: Move work items to a stack list Daniel Wagner
2019-11-13 3:15 ` Martin K. Petersen
2019-11-19 13:28 ` Daniel Wagner
2019-11-19 13:32 ` Daniel Wagner
2019-11-19 17:25 ` James Smart
2019-11-19 18:14 ` Daniel Wagner
2019-11-25 16:40 ` Ewan D. Milne [this message]
2019-11-25 17:06 ` James Smart
2019-11-25 18:23 ` Ewan D. Milne
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=44cc15adc190fb1f6f89cbb8478aadda35f6b1e2.camel@redhat.com \
--to=emilne@redhat.com \
--cc=dick.kennedy@broadcom.com \
--cc=dwagner@suse.de \
--cc=james.smart@broadcom.com \
--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