From: Haoyu Lu <hechushiguitu666@gmail.com>
To: Viresh Kumar <vireshk@kernel.org>
Cc: Damien Le Moal <dlemoal@kernel.org>,
Niklas Cassel <cassel@kernel.org>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
Haoyu Lu <hechushiguitu666@gmail.com>
Subject: [PATCH] ata: pata_arasan_cf: fix missing newline in dev_err messages
Date: Thu, 2 Apr 2026 10:10:26 +0800 [thread overview]
Message-ID: <20260402021027.56-1-hechushiguitu666@gmail.com> (raw)
Add missing trailing newlines to dev_err() messages in pata_arasan_cf.c.
This keeps the error output as properly terminated log lines.
Signed-off-by: Haoyu Lu <hechushiguitu666@gmail.com>
---
drivers/ata/pata_arasan_cf.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/ata/pata_arasan_cf.c b/drivers/ata/pata_arasan_cf.c
index 514d549286b5..abcdef123456 100644
--- a/drivers/ata/pata_arasan_cf.c
+++ b/drivers/ata/pata_arasan_cf.c
@@ -380,7 +380,7 @@ static int arasan_cf_xfer(struct arasan_cf_dev *acdev, struct ata_queued_cmd *qc
if (!wait_for_completion_timeout(&acdev->cf_completion, TIMEOUT)) {
u32 rw = acdev->qc->tf.flags & ATA_TFLAG_WRITE;
- dev_err(acdev->host->dev, "%s TimeOut", rw ? "write" : "read");
+ dev_err(acdev->host->dev, "%s TimeOut\n", rw ? "write" : "read");
return -ETIMEDOUT;
}
@@ -474,7 +474,7 @@ static int arasan_cf_xfer(struct arasan_cf_dev *acdev, struct ata_queued_cmd *qc
dma_len = min(xfer_cnt, FIFO_SIZE);
ret = dma_xfer(acdev, src, dest, dma_len);
if (ret) {
- dev_err(acdev->host->dev, "dma failed");
+ dev_err(acdev->host->dev, "dma failed\n");
goto fail;
}
--
2.17.1
next reply other threads:[~2026-04-02 2:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 2:10 Haoyu Lu [this message]
2026-04-02 3:00 ` [PATCH] ata: pata_arasan_cf: fix missing newline in dev_err messages Viresh Kumar
2026-04-02 5:35 ` Damien Le Moal
2026-04-02 7:11 ` Owens James
2026-04-02 7:38 ` Damien Le Moal
2026-04-02 7:48 ` Haoyu Lu
2026-04-02 8:27 ` Niklas Cassel
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=20260402021027.56-1-hechushiguitu666@gmail.com \
--to=hechushiguitu666@gmail.com \
--cc=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.