From: Wenpeng Liang <liangwenpeng@huawei.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: <leon@kernel.org>, <linux-rdma@vger.kernel.org>, <linuxarm@huawei.com>
Subject: Re: [PATCH for-next 5/5] RDMA/hns: Recover 1bit-ECC error of RAM on chip
Date: Thu, 7 Jul 2022 21:32:21 +0800 [thread overview]
Message-ID: <4d882ff4-08aa-dfbf-e79e-8ea2cdb5c274@huawei.com> (raw)
In-Reply-To: <20220704134935.GA1422797@nvidia.com>
On 2022/7/4 21:49, Jason Gunthorpe wrote:
>> +static const struct {
>> + char *name;
> const char *
>
I will fix it in v2.
>> + ret = hns_roce_cmq_send(hr_dev, &desc, 1);
>> + if (ret) {
>> + dev_err(hr_dev->dev,
>> + "failed to execute cmd to read gmv, ret = %d.\n", ret);
>> + return ret;
> Shouldn't all these prints use the IB version of the loggers?
>
Some types of interrupts may be generated before the ib device
is registered, so all these prints use dev_err().
>> +static irqreturn_t abnormal_interrupt_others(struct hns_roce_dev *hr_dev)
>> +{
>> + struct hns_roce_work *ecc_work;
>> +
>> + ecc_work = kzalloc(sizeof(*ecc_work), GFP_ATOMIC);
>> + if (!ecc_work)
>> + return IRQ_NONE;
>> +
>> + ecc_work->hr_dev = hr_dev;
> Since there is nothing in this work you should just embed it in the
> struct hns_roce_dev and use container_of to get the hr_dev. Then there
> is no allocation here.
>
Fix it in v2.
Thanks,
Wenpeng
> Jason
> .
>
prev parent reply other threads:[~2022-07-07 13:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 11:08 [PATCH for-next 0/5] Supports recovery of on-chip RAM 1bit ECC errors Wenpeng Liang
2022-06-24 11:08 ` [PATCH for-next 1/5] RDMA/hns: Remove unused abnormal interrupt of type RAS Wenpeng Liang
2022-06-24 11:08 ` [PATCH for-next 2/5] RDMA/hns: Fix the wrong type of return value of the interrupt handler Wenpeng Liang
2022-06-24 11:08 ` [PATCH for-next 3/5] RDMA/hns: Fix incorrect clearing of interrupt status register Wenpeng Liang
2022-06-24 11:08 ` [PATCH for-next 4/5] RDMA/hns: Refactor the abnormal interrupt handler function Wenpeng Liang
2022-06-24 11:08 ` [PATCH for-next 5/5] RDMA/hns: Recover 1bit-ECC error of RAM on chip Wenpeng Liang
2022-07-04 13:49 ` Jason Gunthorpe
2022-07-07 13:32 ` 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=4d882ff4-08aa-dfbf-e79e-8ea2cdb5c274@huawei.com \
--to=liangwenpeng@huawei.com \
--cc=jgg@nvidia.com \
--cc=leon@kernel.org \
--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 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.