From: shijie001@208suo.com
To: robh+dt@kernel.org, frowand.list@gmail.com
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] scripts/dtc: Fix errors in yamltree.c
Date: Tue, 18 Jul 2023 09:38:10 +0800 [thread overview]
Message-ID: <40586276d1294a4d8c81db3cd5dcd4ac@208suo.com> (raw)
In-Reply-To: <tencent_C2E29E92E4A5FCCF6F6BB14E2ED98DC6C309@qq.com>
The following checkpatch errors are removed:
ERROR: "(foo*)" should be "(foo *)"
Signed-off-by: Jie Shi <shijie001@208suo.com>
---
scripts/dtc/yamltree.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/scripts/dtc/yamltree.c b/scripts/dtc/yamltree.c
index 55908c829c98..dd22858d1bb1 100644
--- a/scripts/dtc/yamltree.c
+++ b/scripts/dtc/yamltree.c
@@ -57,7 +57,7 @@ static void yaml_propval_int(yaml_emitter_t *emitter,
struct marker *markers,
switch(width) {
case 1:
- sprintf(buf, "0x%"PRIx8, *(uint8_t*)(data + off));
+ sprintf(buf, "0x%"PRIx8, *(uint8_t *)(data + off));
break;
case 2:
sprintf(buf, "0x%"PRIx16, dtb_ld16(data + off));
@@ -80,11 +80,11 @@ static void yaml_propval_int(yaml_emitter_t
*emitter, struct marker *markers,
if (is_phandle)
yaml_scalar_event_initialize(&event, NULL,
- (yaml_char_t*)"!phandle", (yaml_char_t *)buf,
+ (yaml_char_t *)"!phandle", (yaml_char_t *)buf,
strlen(buf), 0, 0, YAML_PLAIN_SCALAR_STYLE);
else
yaml_scalar_event_initialize(&event, NULL,
- (yaml_char_t*)YAML_INT_TAG, (yaml_char_t *)buf,
+ (yaml_char_t *)YAML_INT_TAG, (yaml_char_t *)buf,
strlen(buf), 1, 1, YAML_PLAIN_SCALAR_STYLE);
yaml_emitter_emit_or_die(emitter, &event);
}
@@ -119,7 +119,7 @@ static void yaml_propval(yaml_emitter_t *emitter,
struct property *prop)
/* Emit the property name */
yaml_scalar_event_initialize(&event, NULL,
- (yaml_char_t *)YAML_STR_TAG, (yaml_char_t*)prop->name,
+ (yaml_char_t *)YAML_STR_TAG, (yaml_char_t *)prop->name,
strlen(prop->name), 1, 1, YAML_PLAIN_SCALAR_STYLE);
yaml_emitter_emit_or_die(emitter, &event);
@@ -127,7 +127,7 @@ static void yaml_propval(yaml_emitter_t *emitter,
struct property *prop)
if (len == 0) {
yaml_scalar_event_initialize(&event, NULL,
(yaml_char_t *)YAML_BOOL_TAG,
- (yaml_char_t*)"true",
+ (yaml_char_t *)"true",
strlen("true"), 1, 0, YAML_PLAIN_SCALAR_STYLE);
yaml_emitter_emit_or_die(emitter, &event);
return;
@@ -194,7 +194,7 @@ static void yaml_tree(struct node *tree,
yaml_emitter_t *emitter)
/* Loop over all the children, emitting them into the map */
for_each_child(tree, child) {
yaml_scalar_event_initialize(&event, NULL,
- (yaml_char_t *)YAML_STR_TAG, (yaml_char_t*)child->name,
+ (yaml_char_t *)YAML_STR_TAG, (yaml_char_t *)child->name,
strlen(child->name), 1, 0, YAML_PLAIN_SCALAR_STYLE);
yaml_emitter_emit_or_die(emitter, &event);
yaml_tree(child, emitter);
next parent reply other threads:[~2023-07-18 1:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_C2E29E92E4A5FCCF6F6BB14E2ED98DC6C309@qq.com>
2023-07-18 1:38 ` shijie001 [this message]
2023-07-18 13:42 ` Rob Herring
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=40586276d1294a4d8c81db3cd5dcd4ac@208suo.com \
--to=shijie001@208suo.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®