From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Cai Huoqing <caihuoqing@baidu.com>
Cc: Claudiu Beznea <claudiu.beznea@microchip.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net: cadence: macb: Make use of the helper function dev_err_probe()
Date: Thu, 16 Sep 2021 09:25:45 +0200 [thread overview]
Message-ID: <9318f9be-88f3-5405-11fa-b51a8ada7c2c@microchip.com> (raw)
In-Reply-To: <20210915145804.7357-1-caihuoqing@baidu.com>
On 15/09/2021 at 16:58, Cai Huoqing wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> When possible use dev_err_probe help to properly deal with the
> PROBE_DEFER error, the benefit is that DEFER issue will be logged
> in the devices_deferred debugfs file.
Well, I don't see where the PROBE_DEFER error could be triggered by the
call graph of this function: can you please point me to where this error
could come from?
Best regards,
Nicolas
> And using dev_err_probe() can reduce code size, and simplify the code.
>
> Signed-off-by: Cai Huoqing <caihuoqing@baidu.com>
NACK, for now.
> ---
> drivers/net/ethernet/cadence/macb_pci.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/net/ethernet/cadence/macb_pci.c b/drivers/net/ethernet/cadence/macb_pci.c
> index 8b7b59908a1a..d09c570a15ae 100644
> --- a/drivers/net/ethernet/cadence/macb_pci.c
> +++ b/drivers/net/ethernet/cadence/macb_pci.c
> @@ -35,10 +35,8 @@ static int macb_probe(struct pci_dev *pdev, const struct pci_device_id *id)
>
> /* enable pci device */
> err = pcim_enable_device(pdev);
> - if (err < 0) {
> - dev_err(&pdev->dev, "Enabling PCI device has failed: %d", err);
> - return err;
> - }
> + if (err < 0)
> + return dev_err_probe(&pdev->dev, err, "Enabling PCI device has failed\n");
>
> pci_set_master(pdev);
>
> --
> 2.25.1
>
--
Nicolas Ferre
prev parent reply other threads:[~2021-09-16 7:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 14:58 Cai Huoqing
2021-09-16 7:25 ` Nicolas Ferre [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=9318f9be-88f3-5405-11fa-b51a8ada7c2c@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=caihuoqing@baidu.com \
--cc=claudiu.beznea@microchip.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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®