From: Markus Elfring <Markus.Elfring@web.de>
To: Dan Carpenter <dan.carpenter@linaro.org>,
Jianhao Xu <jianhao.xu@seu.edu.cn>, Zilin Guan <zilin@seu.edu.cn>,
linux-scsi@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Justin Tee <justin.tee@broadcom.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Paul Ely <paul.ely@broadcom.com>
Subject: Re: [1/3] scsi: lpfc: Fix memory leak in lpfc_config_port_post()
Date: Mon, 5 Jan 2026 11:41:03 +0100 [thread overview]
Message-ID: <ce145c7f-33fc-47a7-bcbf-2ec62719047a@web.de> (raw)
In-Reply-To: <aVuP0lJxn2pc6cNa@stanley.mountain>
> I meant "or at least stop complaining about style and grammar issues".
Do any other contributors occasionally get also into the mood to point similar
adjustment opportunities out?
Regards,
Markus
next prev parent reply other threads:[~2026-01-05 10:41 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 ` Markus Elfring [this message]
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
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=ce145c7f-33fc-47a7-bcbf-2ec62719047a@web.de \
--to=markus.elfring@web.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=dan.carpenter@linaro.org \
--cc=jianhao.xu@seu.edu.cn \
--cc=justin.tee@broadcom.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