From: Masami Hiramatsu <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Chen Yu <yu.c.chen@intel.com>, Chen Yu <yu.chen.surf@gmail.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: [RFC PATCH 0/3] bootconfig: Use hexadecimal ASCII string for size and checksum
Date: Thu, 19 Nov 2020 23:31:32 +0900 [thread overview]
Message-ID: <160579629161.503380.9118263439060046721.stgit@devnote2> (raw)
Hello,
Here is a seires of patches to change the bootconfig footer format
to use 8-bytes hexadecimal ASCII string for size and checksum instead
of u32.
In the previous thread for alignment series[1], Steve pointed that
the current footer format makes it hard to apply the bootconfig for
cross-build initrd if the target endianness is different from the
host machine.
So, this changes the size and checksum format to 8-bytes hexadecimal
ASCII string as same as cpio. Since that is a string, we don't need
to care of the difference of the endianness anymore.
Thank you,
[1] https://lore.kernel.org/lkml/20201118112249.30d20147@gandalf.local.home/
---
Masami Hiramatsu (3):
bootconfig: Use hexadecimal ASCII string for size and checksum
tools/bootconfig: Use hexadecimal ASCII string for size and checksum
docs: bootconfig: Use hexadecimal ASCII string for size and checksum
Documentation/admin-guide/bootconfig.rst | 6 +++-
init/main.c | 20 ++++++++++----
tools/bootconfig/main.c | 43 +++++++++++++++++++-----------
tools/bootconfig/test-bootconfig.sh | 2 +
4 files changed, 48 insertions(+), 23 deletions(-)
--
Masami Hiramatsu (Linaro) <mhiramat@kernel.org>
next reply other threads:[~2020-11-19 14:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 14:31 Masami Hiramatsu [this message]
2020-11-19 14:31 ` [RFC PATCH 1/3] bootconfig: Use hexadecimal ASCII string for size and checksum Masami Hiramatsu
2020-11-19 14:31 ` [RFC PATCH 2/3] tools/bootconfig: " Masami Hiramatsu
2020-11-19 14:32 ` [RFC PATCH 3/3] docs: bootconfig: " Masami Hiramatsu
2020-11-19 17:36 ` [RFC PATCH 0/3] " Linus Torvalds
2020-11-19 17:42 ` Steven Rostedt
2020-11-19 23:58 ` Masami Hiramatsu
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=160579629161.503380.9118263439060046721.stgit@devnote2 \
--to=mhiramat@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.org \
--cc=yu.c.chen@intel.com \
--cc=yu.chen.surf@gmail.com \
/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).