lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250928011148.4593-1-daiyanlong@kylinos.cn>
Date: Sun, 28 Sep 2025 09:11:48 +0800
From: YanLong Dai <daiyanlong@...inos.cn>
To: kalesh-anakkur.purayil@...adcom.com,
	yanjun.zhu@...ux.dev
Cc: jgg@...pe.ca,
	leon@...nel.org,
	daiyanlong@...inos.cn,
	dyl_wlc@....com,
	linux-kernel@...r.kernel.org,
	linux-rdma@...r.kernel.org,
	selvin.xavier@...adcom.com
Subject: Re:[PATCH v2 rdma-rc] RDMA/bnxt_re: Fix a potential memory leak in destroy_gsi_sqp

Hi Kalesh, Yanjun

Thank you both for your time and reviews.

On Wed, Sep 24, 2025 at 10:31:34 +0530, Kalesh wrote:
>Hi YanLong,
>
>Few generic guidelines.
>
>1. You should select a target tree in the subject prefix and specify a revision number. Since this is a bug fix, the target tree should be "rdma-rc".
>2. When you send an updated version of the patch, please mention version number. Also, mention the changes made in each version. i.e. under --- you can add extra info that will not be included in the actual commit, e.g. changes between each version of patches.
>
>One comment in line.

Thank you so much for your patience and guidance throughout this process.

I have incorporated all of your suggestions in this v2 version:
- Added the "rdma-rc" target tree prefix in the subject line
- Used proper version numbering (v2)
- Included the changelog below the '---' line as recommended

Gentle ping on this patch.
For easy reference, the patch is available on lore.kernel.org here: 
https://lore.kernel.org/all/20250924061444.11288-1-daiyanlong@kylinos.cn/


---


On Fri, Sep 26, 2025 at 09:11:11AM -0700, Yanjun wrote:
> Hi, YanLong
> 
> In regions where Chinese is not supported, the email may appear garbled. 
> We recommend replacing any Chinese content in the email with the 
> corresponding English to ensure clarity.
> 
> Thanks a lot.
> Yanjun.Zhu

Thank you for the reminder.
I have replaced all the Chinese content in my previous email with English to ensure clarity and avoid any encoding issues.


Best regards,
YanLong Dai


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ