From: Dan Carpenter <dan.carpenter@linaro.org>
To: Justin Tee <justintee8345@gmail.com>
Cc: Zilin Guan <zilin@seu.edu.cn>,
justin.tee@broadcom.com, paul.ely@broadcom.com,
James.Bottomley@hansenpartnership.com,
martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, jianhao.xu@seu.edu.cn
Subject: Re: [PATCH 0/3] scsi: lpfc: Fix multiple memory leaks in error paths
Date: Mon, 5 Jan 2026 12:56:38 +0300 [thread overview]
Message-ID: <aVuK1oAoM1smyG8_@stanley.mountain> (raw)
In-Reply-To: <CABPRKS8=__+4TcW9wjzHuVSZa7wKhJpzT4VGubBHet4TSc-u7w@mail.gmail.com>
On Mon, Dec 29, 2025 at 06:04:01PM -0800, Justin Tee wrote:
> Hi Zilin,
>
> For this patch set, please see and attend to Markus’ comments.
You should provide a link to lore because a lot of people have blocked
Markus so we don't see it in our inboxes.
regards,
dan carpenter
prev parent reply other threads:[~2026-01-05 9:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-29 7:15 [PATCH 0/3] scsi: lpfc: Fix multiple memory leaks in error paths Zilin Guan
2025-12-29 7:15 ` [PATCH 1/3] scsi: lpfc: Fix memory leak in lpfc_config_port_post() Zilin Guan
2025-12-29 9:09 ` Markus Elfring
2025-12-30 6:20 ` Zilin Guan
2025-12-30 7:28 ` [1/3] " Markus Elfring
2025-12-30 9:05 ` Zilin Guan
2026-01-05 9:53 ` [PATCH 1/3] " Dan Carpenter
2026-01-05 10:17 ` Dan Carpenter
2026-01-05 10:41 ` [1/3] " Markus Elfring
2025-12-29 7:15 ` [PATCH 2/3] scsi: lpfc: Fix memory leak in lpfc_sli4_driver_resource_setup() Zilin Guan
2025-12-29 7:15 ` [PATCH 3/3] scsi: lpfc: Fix memory leak in lpfc_cmpl_plogi_plogi_issue() Zilin Guan
2025-12-30 2:04 ` [PATCH 0/3] scsi: lpfc: Fix multiple memory leaks in error paths Justin Tee
2025-12-30 3:05 ` Zilin Guan
2026-01-05 9:56 ` Dan Carpenter [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=aVuK1oAoM1smyG8_@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=jianhao.xu@seu.edu.cn \
--cc=justin.tee@broadcom.com \
--cc=justintee8345@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=paul.ely@broadcom.com \
--cc=zilin@seu.edu.cn \
/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