From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: YanLong Dai <daiyanlong@kylinos.cn>, kalesh-anakkur.purayil@broadcom.com
Cc: jgg@ziepe.ca, leon@kernel.org, dyl_wlc@163.com,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
selvin.xavier@broadcom.com
Subject: Re: [PATCH v2 rdma-rc] RDMA/bnxt_re: Fix a potential memory leak in destroy_gsi_sqp
Date: Sat, 27 Sep 2025 19:06:43 -0700 [thread overview]
Message-ID: <4aba00a3-cc60-4512-9e84-49c08817edbb@linux.dev> (raw)
In-Reply-To: <20250928011148.4593-1-daiyanlong@kylinos.cn>
在 2025/9/27 18:11, YanLong Dai 写道:
> 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.
Thanks a lot. The mail looks better. I am fine with this.
Yanjun.Zhu
>
>
> Best regards,
> YanLong Dai
>
--
Best Regards,
Yanjun.Zhu
next prev parent reply other threads:[~2025-09-28 2:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 2:39 回复: Re: [PATCH v2 rdma-rc] RDMA/bnxt_re: Fix a potential memory leak in destroy_gsi_sqp 代彦龙
2025-09-26 16:11 ` åå¤: " yanjun.zhu
2025-09-28 1:11 ` YanLong Dai
2025-09-28 2:06 ` Zhu Yanjun [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-24 6:33 [PATCH " 代彦龙
2025-09-24 6:14 YanLong Dai
2025-10-19 10:48 ` Leon Romanovsky
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=4aba00a3-cc60-4512-9e84-49c08817edbb@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=daiyanlong@kylinos.cn \
--cc=dyl_wlc@163.com \
--cc=jgg@ziepe.ca \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=selvin.xavier@broadcom.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 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.