From: elfring@users.sourceforge.net (SF Markus Elfring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: dmabounce: Combine substrings for two messages
Date: Thu, 1 Jun 2017 18:02:15 +0200 [thread overview]
Message-ID: <f31af146-5988-6834-8a38-a274da70cf95@users.sourceforge.net> (raw)
In-Reply-To: <697e7810-d280-08f3-2a24-026ff41e15a3@users.sourceforge.net>
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Thu, 1 Jun 2017 17:23:52 +0200
The script "checkpatch.pl" pointed information out like the following.
WARNING: quoted string split across lines
Thus fix the affected source code places.
Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
---
arch/arm/common/dmabounce.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/arm/common/dmabounce.c b/arch/arm/common/dmabounce.c
index 9ef7ab64b3d8..e2fbdab41810 100644
--- a/arch/arm/common/dmabounce.c
+++ b/arch/arm/common/dmabounce.c
@@ -227,8 +227,9 @@ static int needs_bounce(struct device *dev, dma_addr_t dma_addr, size_t size)
limit = (mask + 1) & ~mask;
if (limit && size > limit) {
- dev_err(dev, "DMA mapping too big (requested %#x "
- "mask %#Lx)\n", size, *dev->dma_mask);
+ dev_err(dev,
+ "DMA mapping too big (requested %#x mask %#Lx)\n",
+ size, *dev->dma_mask);
return -E2BIG;
}
@@ -546,8 +547,7 @@ void dmabounce_unregister_dev(struct device *dev)
if (!device_info) {
dev_warn(dev,
- "Never registered with dmabounce but attempting"
- "to unregister!\n");
+ "Never registered with dmabounce but attempting to unregister!\n");
return;
}
--
2.13.0
prev parent reply other threads:[~2017-06-01 16:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 15:56 [PATCH 0/3] ARM: dmabounce: Adjustments for four function implementations SF Markus Elfring
2017-06-01 15:59 ` [PATCH 1/3] ARM: dmabounce: Improve a size determination in two functions SF Markus Elfring
2017-06-01 16:00 ` [PATCH 2/3] ARM: dmabounce: Delete an error message for a failed memory allocation " SF Markus Elfring
2017-06-01 16:02 ` SF Markus Elfring [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=f31af146-5988-6834-8a38-a274da70cf95@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).