From: elfring@users.sourceforge.net (SF Markus Elfring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM: dmabounce: Adjustments for four function implementations
Date: Thu, 1 Jun 2017 17:56:20 +0200 [thread overview]
Message-ID: <697e7810-d280-08f3-2a24-026ff41e15a3@users.sourceforge.net> (raw)
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Thu, 1 Jun 2017 17:34:56 +0200
A few update suggestions were taken into account
from static source code analysis.
Markus Elfring (3):
Improve a size determination in two functions
Delete an error message for a failed memory allocation in two functions
Combine substrings for two messages
arch/arm/common/dmabounce.c | 21 ++++++++-------------
1 file changed, 8 insertions(+), 13 deletions(-)
--
2.13.0
next reply other threads:[~2017-06-01 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 15:56 SF Markus Elfring [this message]
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 ` [PATCH 3/3] ARM: dmabounce: Combine substrings for two messages SF Markus Elfring
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=697e7810-d280-08f3-2a24-026ff41e15a3@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).