From: Matthias Brugger <matthias.bgg@gmail.com>
To: 刘紫琴 <ziqin_l@hust.edu.cn>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>
Cc: Dongliang Mu <dzm91@hust.edu.cn>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] soc: mediatek: mtk-svs: change the function IS_ERR_OR_NULL() to IS_ERR()
Date: Thu, 13 Apr 2023 11:37:12 +0200 [thread overview]
Message-ID: <a311d52c-a07a-fdfe-5b48-502d05f70737@gmail.com> (raw)
In-Reply-To: <1b48b0ec.3b004.1877971d059.Coremail.ziqin_l@hust.edu.cn>
On 13/04/2023 09:08, 刘紫琴 wrote:
> ping?
>
Please be patient, maintainers are sometimes busy and can't cope with all the
patches at a time.
Please don't top post :)
This was already fixed and applied to linux-next via
https://lore.kernel.org/all/20230202124104.16504-2-roger.lu@mediatek.com/
Best regards,
Matthias
> "Ziqin Liu" <ziqin_l@hust.edu.cn>写道:
>> nvmem_cell_get() will return an ERR_PTR() on error or a valid pointer to a
>> struct nvmem_cell but won't return NULL, the check function should be
>> IS_ERR() instead of IS_ERR_OR_NULL()
>>
>> Signed-off-by: Ziqin Liu <ziqin_l@hust.edu.cn>
>> Reviewed-by: Dongliang Mu <dzm91@hust.edu.cn>
>> ---
>> drivers/soc/mediatek/mtk-svs.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/soc/mediatek/mtk-svs.c b/drivers/soc/mediatek/mtk-svs.c
>> index a7eb019b5157..8127fb6d587b 100644
>> --- a/drivers/soc/mediatek/mtk-svs.c
>> +++ b/drivers/soc/mediatek/mtk-svs.c
>> @@ -1726,7 +1726,7 @@ static int svs_get_efuse_data(struct svs_platform *svsp,
>> struct nvmem_cell *cell;
>>
>> cell = nvmem_cell_get(svsp->dev, nvmem_cell_name);
>> - if (IS_ERR_OR_NULL(cell)) {
>> + if (IS_ERR(cell)) {
>> dev_err(svsp->dev, "no \"%s\"? %ld\n",
>> nvmem_cell_name, PTR_ERR(cell));
>> return PTR_ERR(cell);
>> --
>> 2.25.1
prev parent reply other threads:[~2023-04-13 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 2:42 Ziqin Liu
2023-04-13 7:08 ` 刘紫琴
2023-04-13 9:37 ` Matthias Brugger [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=a311d52c-a07a-fdfe-5b48-502d05f70737@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=dzm91@hust.edu.cn \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=ziqin_l@hust.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
all inboxes | Powered by JetHome®