From: eric.long@linaro.org (Eric Long)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH 2/2] coresight: Remove the mistakes detected by smatch tool
Date: Wed, 20 Jan 2016 14:39:13 +0800 [thread overview]
Message-ID: <a9a6dbebe9fa624b3049c9de0b64462e4e1f1a80.1453271739.git.eric.long@linaro.org> (raw)
In-Reply-To: <cover.1453271738.git.eric.long@linaro.org>
There is an unnecessary space at the front of the code.
The smatch tool output logs as the following:
of_coresight.c:89 of_coresight_alloc_memory() warn:
inconsistent indenting
Signed-off-by: Eric Long <eric.long@linaro.org>
---
drivers/hwtracing/coresight/of_coresight.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hwtracing/coresight/of_coresight.c b/drivers/hwtracing/coresight/of_coresight.c
index b097361..3cc57c1 100644
--- a/drivers/hwtracing/coresight/of_coresight.c
+++ b/drivers/hwtracing/coresight/of_coresight.c
@@ -86,7 +86,7 @@ static int of_coresight_alloc_memory(struct device *dev,
return -ENOMEM;
/* Children connected to this component via @outports */
- pdata->child_names = devm_kzalloc(dev, pdata->nr_outport *
+ pdata->child_names = devm_kzalloc(dev, pdata->nr_outport *
sizeof(*pdata->child_names),
GFP_KERNEL);
if (!pdata->child_names)
--
1.7.9.5
next prev parent reply other threads:[~2016-01-20 6:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 6:39 [RESEND PATCH 0/2] Remove the mistakes detected by the check tools Eric Long
2016-01-20 6:39 ` [RESEND PATCH 1/2] coresight: tmc/etm4x: Remove the mistakes detected by sparse tool Eric Long
2016-01-20 6:39 ` Eric Long [this message]
2016-01-21 16:56 ` [RESEND PATCH 0/2] Remove the mistakes detected by the check tools Mathieu Poirier
2016-01-22 9:15 ` Eric Long
2016-01-22 17:29 ` Mathieu Poirier
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=a9a6dbebe9fa624b3049c9de0b64462e4e1f1a80.1453271739.git.eric.long@linaro.org \
--to=eric.long@linaro.org \
--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).