From: Damien Le Moal <dlemoal@kernel.org>
To: 杜敏杰 <duminjie@vivo.com>, "Viresh Kumar" <vireshk@kernel.org>,
"Sergey Shtylyov" <s.shtylyov@omp.ru>,
"open list:LIBATA PATA ARASAN COMPACT FLASH CONTROLLER"
<linux-ide@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>
Cc: "opensource.kernel" <opensource.kernel@vivo.com>
Subject: Re: [PATCH v3] ata: pata_arasan_cf: Use dev_err_probe() instead dev_err() in data_xfer()
Date: Wed, 19 Jul 2023 19:14:33 +0900 [thread overview]
Message-ID: <9c1b702d-fdee-b7c0-9e79-4822f0d2340b@kernel.org> (raw)
In-Reply-To: <20230719100322.6164-1-duminjie@vivo.com>
On 7/19/23 19:03, 杜敏杰 wrote:
> It is possible for dma_request_chan() to return EPROBE_DEFER, which means
> acdev->host->dev is not ready yet.
> At this point dev_err() will have no output.
>
> Signed-off-by: Minjie Du <duminjie@vivo.com>
> ---
> V1 - V3:
> Fix code format.
> ---
> drivers/ata/pata_arasan_cf.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/ata/pata_arasan_cf.c b/drivers/ata/pata_arasan_cf.c
> index 6ab294322..c85932c20 100644
> --- a/drivers/ata/pata_arasan_cf.c
> +++ b/drivers/ata/pata_arasan_cf.c
> @@ -529,7 +529,8 @@ static void data_xfer(struct work_struct *work)
> /* dma_request_channel may sleep, so calling from process context */
> acdev->dma_chan = dma_request_chan(acdev->host->dev, "data");
> if (IS_ERR(acdev->dma_chan)) {
> - dev_err(acdev->host->dev, "Unable to get dma_chan\n");
> + dev_err_probe(acdev->host->dev, PTR_ERR(acdev->dma_chan),
> + "Unable to get dma_chan\n")
Seriously ? You keep resending the same. Still not aligned. And even
worse: this will not even compile as this is missing ";".
Please improve your process and (1) act on comments and (2) properly
test your changes.
> acdev->dma_chan = NULL;
> goto chan_request_fail;
> }
--
Damien Le Moal
Western Digital Research
parent reply other threads:[~2023-07-19 10:14 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230719100322.6164-1-duminjie@vivo.com>]
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=9c1b702d-fdee-b7c0-9e79-4822f0d2340b@kernel.org \
--to=dlemoal@kernel.org \
--cc=duminjie@vivo.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=opensource.kernel@vivo.com \
--cc=s.shtylyov@omp.ru \
--cc=vireshk@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®