From: Brian King <brking@linux.vnet.ibm.com>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
Wen Xiong <wenxiong@us.ibm.com>,
kexec@lists.infradead.org, ebiederm@xmission.com
Subject: [PATCH 2/3] kexec: Export kexec_in_progress
Date: Tue, 20 May 2014 10:35:38 -0500 [thread overview]
Message-ID: <537B764A.7040801@linux.vnet.ibm.com> (raw)
Export kexec_in_progress for use by device drivers and other modules
to optimize kexec boot.
Signed-off-by: Brian King <brking@linux.vnet.ibm.com>
---
kernel/kexec.c | 2 ++
1 file changed, 2 insertions(+)
diff -puN kernel/kexec.c~kexec_export_in_prog kernel/kexec.c
--- linux/kernel/kexec.c~kexec_export_in_prog 2014-05-13 16:59:19.000000000 -0500
+++ linux-bjking1/kernel/kexec.c 2014-05-13 16:59:19.000000000 -0500
@@ -1712,3 +1712,5 @@ int kernel_kexec(void)
mutex_unlock(&kexec_mutex);
return error;
}
+
+EXPORT_SYMBOL_GPL(kexec_in_progress);
_
reply other threads:[~2014-05-20 15:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=537B764A.7040801@linux.vnet.ibm.com \
--to=brking@linux.vnet.ibm.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=ebiederm@xmission.com \
--cc=kexec@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=wenxiong@us.ibm.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).