From: "tip-bot for H. Peter Anvin" <hpa@linux.intel.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@kernel.org,
yinghai@kernel.org, tglx@linutronix.de, hpa@linux.intel.com,
ebiederm@xmission.com
Subject: [tip:x86/urgent] x86, doc: Add a formal bootloader ID for kexec-tools
Date: Wed, 12 Dec 2012 20:38:25 -0800 [thread overview]
Message-ID: <tip-4bfe24ac1d9d9f06b30b2909f53ea462c72cfe1d@git.kernel.org> (raw)
In-Reply-To: <50C95832.5030306@zytor.com>
Commit-ID: 4bfe24ac1d9d9f06b30b2909f53ea462c72cfe1d
Gitweb: http://git.kernel.org/tip/4bfe24ac1d9d9f06b30b2909f53ea462c72cfe1d
Author: H. Peter Anvin <hpa@linux.intel.com>
AuthorDate: Wed, 12 Dec 2012 20:24:12 -0800
Committer: H. Peter Anvin <hpa@linux.intel.com>
CommitDate: Wed, 12 Dec 2012 20:25:43 -0800
x86, doc: Add a formal bootloader ID for kexec-tools
Add bootloader id D for kexec-tools (it is kexec-tools, not the kexec
system call, that builds the data structures, therefore it is
kexec-tools which is the "bootloader" for this purpose.)
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
Cc: Eric W. Biederman <ebiederm@xmission.com>
Cc: Yinghai Lu <yinghai@kernel.org>
Link: http://lkml.kernel.org/r/50C95832.5030306@zytor.com
---
Documentation/x86/boot.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/x86/boot.txt b/Documentation/x86/boot.txt
index 9efceff..c25a53e 100644
--- a/Documentation/x86/boot.txt
+++ b/Documentation/x86/boot.txt
@@ -381,6 +381,7 @@ Protocol: 2.00+
A Gujin
B Qemu
C Arcturus Networks uCbootloader
+ D kexec-tools
E Extended (see ext_loader_type)
F Special (0xFF = undefined)
10 Reserved
next prev parent reply other threads:[~2012-12-13 4:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 1:57 kexec and struct boot_params H. Peter Anvin
2012-12-06 3:12 ` Yinghai Lu
2012-12-07 6:57 ` Yinghai Lu
2012-12-13 2:49 ` Yinghai Lu
2012-12-13 4:23 ` H. Peter Anvin
2012-12-13 4:38 ` tip-bot for H. Peter Anvin [this message]
2012-12-13 6:55 ` Yinghai Lu
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=tip-4bfe24ac1d9d9f06b30b2909f53ea462c72cfe1d@git.kernel.org \
--to=hpa@linux.intel.com \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=yinghai@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
Powered by JetHome