From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Ranjan Kumar <ranjan.kumar@broadcom.com>,
Sreekanth Reddy <sreekanth.reddy@broadcom.com>
Cc: Tomas Henzl <thenzl@redhat.com>,
linux-scsi@vger.kernel.org, sathya.prakash@broadcom.com
Subject: Re: [PATCH v2 0/6] scsi: mpi3mr: fix few resource leaks
Date: Mon, 06 Mar 2023 20:43:23 -0500 [thread overview]
Message-ID: <yq1h6uxmj5s.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20230302234336.25456-1-thenzl@redhat.com> (Tomas Henzl's message of "Fri, 3 Mar 2023 00:43:30 +0100")
Ranjan/Sreekanth,
> The series applies on
> [PATCH 00/15] mpi3mr: Few Enhancements and minor fixes
> from 2/24 posted by Ranjan.
>
> V2 - fixed a bug in [PATCH 5/6]
>
>
> drivers/scsi/mpi3mr/mpi3mr.h | 2 ++
> drivers/scsi/mpi3mr/mpi3mr_fw.c | 50 ++++++++++++++++----------
> drivers/scsi/mpi3mr/mpi3mr_os.c | 24 +++++++++++++
> drivers/scsi/mpi3mr/mpi3mr_transport.c | 5 +--
> 4 files changed, 58 insertions(+), 23 deletions(-)
Please review!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2023-03-07 1:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 23:43 [PATCH v2 0/6] scsi: mpi3mr: fix few resource leaks Tomas Henzl
2023-03-02 23:43 ` [PATCH v2 1/6] scsi: mpi3mr: fix a memory leak Tomas Henzl
2023-03-02 23:43 ` [PATCH v2 2/6] scsi: mpi3mr: fix a dma " Tomas Henzl
2023-03-02 23:43 ` [PATCH v2 3/6] scsi: mpi3mr: fix a " Tomas Henzl
2023-03-02 23:43 ` [PATCH v2 4/6] " Tomas Henzl
2023-03-02 23:43 ` [PATCH v2 5/6] " Tomas Henzl
2023-03-02 23:43 ` [PATCH v2 6/6] " Tomas Henzl
2023-03-07 1:43 ` Martin K. Petersen [this message]
2023-03-07 20:14 ` [PATCH v2 0/6] scsi: mpi3mr: fix few resource leaks Sathya Prakash Veerichetty
2023-03-10 3:13 ` Martin K. Petersen
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=yq1h6uxmj5s.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=linux-scsi@vger.kernel.org \
--cc=ranjan.kumar@broadcom.com \
--cc=sathya.prakash@broadcom.com \
--cc=sreekanth.reddy@broadcom.com \
--cc=thenzl@redhat.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