[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e1f96f77-cf44-7783-bf88-0814bbabbfbc@omp.ru>
Date: Thu, 21 Oct 2021 11:37:09 +0300
From: Sergey Shtylyov <s.shtylyov@....ru>
To: Zheyu Ma <zheyuma97@...il.com>, <damien.lemoal@...nsource.wdc.com>
CC: <linux-ide@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ata: sata_mv: Fix the return value of the probe function
On 21.10.2021 8:57, Zheyu Ma wrote:
> mv_init_host() propagates the value returned by mv_chip_id() which in turn
> gets propagated by mv_pci_init_one() and hits local_pci_probe().
>
> During the process of driver probing, the probe function should return < 0
> for failure, otherwise, the kernel will treat value > 0 as success.
>
> Signed-off-by: Zheyu Ma <zheyuma97@...il.com>
> ---
> drivers/ata/sata_mv.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/ata/sata_mv.c b/drivers/ata/sata_mv.c
> index 9d86203e1e7a..7461fe078dd1 100644
> --- a/drivers/ata/sata_mv.c
> +++ b/drivers/ata/sata_mv.c
> @@ -3897,7 +3897,7 @@ static int mv_chip_id(struct ata_host *host, unsigned int board_idx)
>
> default:
> dev_err(host->dev, "BUG: invalid board index %u\n", board_idx);
> - return 1;
> + return -ENODEV;
Doesn't -EINVAL fit better here?
[...]
MBR, Sergey
Powered by blists - more mailing lists