Since platform_get_irq_byname() never returned zero, so it need not to
check whether it returned zero, it returned -EINVAL or -ENXIO when
failed, so we replace the return error code with the result it returned.
Signed-off-by: Zhu Wang <redacted>
---
drivers/net/ethernet/microchip/lan966x/lan966x_main.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
From: Simon Horman <horms@kernel.org> Date: 2023-08-03 14:32:53
On Thu, Aug 03, 2023 at 04:29:00PM +0800, Zhu Wang wrote:
Since platform_get_irq_byname() never returned zero, so it need not to
check whether it returned zero, it returned -EINVAL or -ENXIO when
failed, so we replace the return error code with the result it returned.
Signed-off-by: Zhu Wang <redacted>
For non-bugfix Networking patches, it is appropriate to
designate the target tree as 'net-next' rather than '-next'.
(For bug fixes 'net' is appropriate).
Link: https://docs.kernel.org/process/maintainer-netdev.html
Otherwise, this looks fine to me.
Reviewed-by: Simon Horman <horms@kernel.org>
[Some people who received this message don't often get email from wangzhu9@huawei.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
Since platform_get_irq_byname() never returned zero, so it need not to
check whether it returned zero, it returned -EINVAL or -ENXIO when
failed, so we replace the return error code with the result it returned.
Signed-off-by: Zhu Wang <redacted>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller [off-list ref]:
On Thu, 3 Aug 2023 16:29:00 +0800 you wrote:
Since platform_get_irq_byname() never returned zero, so it need not to
check whether it returned zero, it returned -EINVAL or -ENXIO when
failed, so we replace the return error code with the result it returned.
Signed-off-by: Zhu Wang <redacted>
---
drivers/net/ethernet/microchip/lan966x/lan966x_main.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)