From: elfring@users.sourceforge.net (SF Markus Elfring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] hwtracing-coresight: Fine-tuning for two function implementations
Date: Thu, 27 Apr 2017 21:45:17 +0200 [thread overview]
Message-ID: <52619d05-65c4-149d-f355-cf9c037a0c9b@users.sourceforge.net> (raw)
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Thu, 27 Apr 2017 21:34:32 +0200
Two update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Use devm_kcalloc() in stm_probe()
Use devm_kcalloc() in of_coresight_alloc_memory()
drivers/hwtracing/coresight/coresight-stm.c | 6 +++---
drivers/hwtracing/coresight/of_coresight.c | 6 +++---
2 files changed, 6 insertions(+), 6 deletions(-)
--
2.12.2
next reply other threads:[~2017-04-27 19:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 19:45 SF Markus Elfring [this message]
2017-04-27 19:46 ` [PATCH 1/2] coresight-stm: Use devm_kcalloc() in stm_probe() SF Markus Elfring
2017-04-27 19:47 ` [PATCH 2/2] of_coresight: Use devm_kcalloc() in of_coresight_alloc_memory() 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=52619d05-65c4-149d-f355-cf9c037a0c9b@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).