From: Wenpeng Liang <liangwenpeng@huawei.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: <dledford@redhat.com>, <linux-rdma@vger.kernel.org>,
<linuxarm@huawei.com>
Subject: Re: [PATCH for-next 0/3] RDMA/hns: Fix some errors in the congestion control algorithm
Date: Thu, 26 Aug 2021 19:41:35 +0800 [thread overview]
Message-ID: <a0cbe12f-1dbd-7bc4-309e-16a35ff0ba90@huawei.com> (raw)
In-Reply-To: <20210825175059.GD1200145@nvidia.com>
On 2021/8/26 1:50, Jason Gunthorpe wrote:
> On Wed, Aug 25, 2021 at 05:43:09PM +0800, Wenpeng Liang wrote:
>> Fix three dip_idx related errors.
>>
>> Junxian Huang (3):
>> RDMA/hns: Bugfix for data type of dip_idx
>> RDMA/hns: Bugfix for the missing assignment for dip_idx
>> RDMA/hns: Bugfix for incorrect association between dip_idx and dgid
>
> Applied to for-next
>
> Please do not put a blank line after Fixes:, it needs to be part of
> the trailer block to parse properly. I fixed it
>
> Thanks,
> Jason
> .
>
Sorry, I forgot to delete the blank line when submitting the commit,
I will pay more attention to it in the future.
Thanks,
Wenpeng
prev parent reply other threads:[~2021-08-26 11:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 9:43 [PATCH for-next 0/3] RDMA/hns: Fix some errors in the congestion control algorithm Wenpeng Liang
2021-08-25 9:43 ` [PATCH for-next 1/3] RDMA/hns: Bugfix for data type of dip_idx Wenpeng Liang
2021-08-25 9:43 ` [PATCH for-next 2/3] RDMA/hns: Bugfix for the missing assignment for dip_idx Wenpeng Liang
2021-08-25 9:43 ` [PATCH for-next 3/3] RDMA/hns: Bugfix for incorrect association between dip_idx and dgid Wenpeng Liang
2021-08-25 17:50 ` [PATCH for-next 0/3] RDMA/hns: Fix some errors in the congestion control algorithm Jason Gunthorpe
2021-08-26 11:41 ` Wenpeng Liang [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=a0cbe12f-1dbd-7bc4-309e-16a35ff0ba90@huawei.com \
--to=liangwenpeng@huawei.com \
--cc=dledford@redhat.com \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@huawei.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;
as well as URLs for NNTP newsgroup(s).