[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Fri, 2 Feb 2024 08:57:02 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Dan Carpenter <dan.carpenter@...aro.org>, linux-fpga@...r.kernel.org,
kernel-janitors@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Moritz Fischer <mdf@...nel.org>, Tom Rix <trix@...hat.com>,
Wu Hao <hao.wu@...el.com>, Xu Yilun <yilun.xu@...el.com>
Cc: LKML <linux-kernel@...r.kernel.org>, Kunwu Chan <chentao@...inos.cn>
Subject: Re: fpga: dfl: fme: Return directly after a failed devm_kasprintf()
call in fme_perf_pmu_register()
>> Thus return directly after a failed devm_kasprintf() call.
>>
>> Fixes: 724142f8c42a7 ("fpga: dfl: fme: add performance reporting support")
>
> This basically doesn't affect runtime because perf_pmu_register() checks for NULL
https://elixir.bootlin.com/linux/v6.8-rc2/source/kernel/events/core.c#L11527
Do you prefer the usage of the error code “-ENOMEM” instead of “-EINVAL”
as an indication for a failed memory allocation?
> so no need for a Fixes tag.
Does the selection of a more appropriate error code qualify for this tag?
Regards,
Markus
Powered by blists - more mailing lists