From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bart Van Assche <bart.vanassche@wdc.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>,
Himanshu Madhani <himanshu.madhani@cavium.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 0/6] Six qla2xxx and qla4xxx patches
Date: Tue, 06 Feb 2018 19:58:41 -0500 [thread overview]
Message-ID: <yq1po5h1upq.fsf@oracle.com> (raw)
In-Reply-To: <20180124003351.2616-1-bart.vanassche@wdc.com> (Bart Van Assche's message of "Tue, 23 Jan 2018 16:33:45 -0800")
Bart,
> The patches in this series are what I came up with after having
> analyzed the source code of the qla[24]xxx drivers with several source
> code analysis tools (scripts/kernel-doc, gcc, sparse and smatch). None
> of the patches in this series have been tested. Yet I'm asking you to
> consider at least the first patch of this series for kernel v4.16
> because it fixes a locking bug in one of the SCSI patches queued for
> kernel v4.16.
Applied to my staging tree for 4.17/scsi-queue. Thanks!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2018-02-07 1:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 0:33 [PATCH 0/6] Six qla2xxx and qla4xxx patches Bart Van Assche
2018-01-24 0:33 ` [PATCH 1/6] qla2xxx: Fix a locking imbalance in qlt_24xx_handle_els() Bart Van Assche
2018-02-07 0:29 ` Martin K. Petersen
2018-01-24 0:33 ` [PATCH 2/6] qla2xxx: Use %p for printing pointers Bart Van Assche
2018-01-24 0:33 ` [PATCH 3/6] qla2xxx: Remove unused symbols Bart Van Assche
2018-01-24 0:33 ` [PATCH 4/6] qla4xxx: " Bart Van Assche
2018-01-24 0:33 ` [PATCH 5/6] qla4xxx: Move an array from a .h into a .c file Bart Van Assche
2018-01-24 0:33 ` [PATCH 6/6] qla2xxx: Fix function argument descriptions Bart Van Assche
2018-01-31 3:04 ` [PATCH 0/6] Six qla2xxx and qla4xxx patches Martin K. Petersen
2018-01-31 5:57 ` Madhani, Himanshu
2018-02-07 0:58 ` Martin K. Petersen [this message]
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=yq1po5h1upq.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=bart.vanassche@wdc.com \
--cc=himanshu.madhani@cavium.com \
--cc=jejb@linux.vnet.ibm.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.