From: Daniel Schaefer <daniel.schaefer@hpe.com>
To: opensbi@lists.infradead.org
Subject: [PATCH v2 1/3] lib: utils: Add strncpy macro to libfdt_env.h
Date: Wed, 19 May 2021 15:54:08 +0800 [thread overview]
Message-ID: <20210519075410.8520-2-daniel.schaefer@hpe.com> (raw)
In-Reply-To: <20210519075410.8520-1-daniel.schaefer@hpe.com>
Just like 2845d2d2cf4fb74a89452ba223995aa4a118c07e
we want to use sbi_strncpy as strncpy in the OpenSBI implementation for
libfdt.
Cc: Abner Chang <abner.chang@hpe.com>
Cc: Anup Patel <Anup.Patel@wdc.com>
Signed-off-by: Daniel Schaefer <daniel.schaefer@hpe.com>
Reviewed-by: Abner Chang <abner.chang@hpe.com>
---
lib/utils/libfdt/libfdt_env.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/lib/utils/libfdt/libfdt_env.h b/lib/utils/libfdt/libfdt_env.h
index bc3e7588660a..f9d9c6783c52 100644
--- a/lib/utils/libfdt/libfdt_env.h
+++ b/lib/utils/libfdt/libfdt_env.h
@@ -31,6 +31,7 @@
#define strchr sbi_strchr
#define strrchr sbi_strrchr
#define strcpy sbi_strcpy
+#define strncpy sbi_strncpy
#define strcmp sbi_strcmp
#define strncmp sbi_strncmp
#define strlen sbi_strlen
--
2.30.1
next prev parent reply other threads:[~2021-05-19 7:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 7:54 [PATCH v2 0/3] Don't use SBI functions in fdt code Daniel Schaefer
2021-05-19 7:54 ` Daniel Schaefer [this message]
2021-05-19 8:37 ` [PATCH v2 1/3] lib: utils: Add strncpy macro to libfdt_env.h Xiang W
2021-05-19 12:51 ` Anup Patel
2021-05-19 12:54 ` Anup Patel
2021-05-19 7:54 ` [PATCH v2 2/3] lib: fdt: Don't use sbi_string functions Daniel Schaefer
2021-05-19 8:38 ` Xiang W
2021-05-19 12:52 ` Anup Patel
2021-05-19 12:54 ` Anup Patel
2021-05-19 7:54 ` [PATCH v2 3/3] lib: utils: Replace strcmp with strncmp Daniel Schaefer
2021-05-19 12:52 ` Anup Patel
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=20210519075410.8520-2-daniel.schaefer@hpe.com \
--to=daniel.schaefer@hpe.com \
--cc=opensbi@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