From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Arun Easi <aeasi@marvell.com>
Cc: "Elliott\, Robert \(Servers\)" <elliott@hpe.com>,
Himanshu Madhani <hmadhani@marvell.com>,
"James.Bottomley\@HansenPartnership.com"
<James.Bottomley@HansenPartnership.com>,
"martin.petersen\@oracle.com" <martin.petersen@oracle.com>,
"linux-scsi\@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH v4] qla2xxx: Fix unbound NVME response length
Date: Wed, 22 Jan 2020 21:06:03 -0500 [thread overview]
Message-ID: <yq1d0bbexkk.fsf@oracle.com> (raw)
In-Reply-To: <alpine.LRH.2.21.9999.2001221611360.15850@irv1user01.caveonetworks.com> (Arun Easi's message of "Wed, 22 Jan 2020 16:20:17 -0800")
Arun,
> I can post a follow on patch, with the WARN/log message under driver
> debug.
Just send a v5. Thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2020-01-23 2:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 19:27 [PATCH v4] qla2xxx: Fix unbound NVME response length Himanshu Madhani
2020-01-22 21:23 ` Ewan D. Milne
2020-01-22 23:18 ` Martin K. Petersen
2020-01-22 23:59 ` Elliott, Robert (Servers)
2020-01-23 0:20 ` Arun Easi
2020-01-23 2:06 ` Martin K. Petersen [this message]
2020-01-23 22:51 ` [EXT] " Arun Easi
2020-01-23 23:21 ` 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=yq1d0bbexkk.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=aeasi@marvell.com \
--cc=elliott@hpe.com \
--cc=hmadhani@marvell.com \
--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.