kexec_load.2: Edits after review comments by Vivek Goyal

Reviewed-by: Vivek Goyal <vgoyal@redhat.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

diff --git a/man2/kexec_load.2 b/man2/kexec_load.2
index 3273e0557f8f3bea2549b25cd0b5f742685f8423..c275fad037cbe404f4d885c9dba071d707d9b49d 100644 (file)
--- a/man2/kexec_load.2
+++ b/man2/kexec_load.2
@@ -34,10 +34,7 @@ kexec_load, kexec_file_load \- load a new kernel for later execution
 .BI "                struct kexec_segment *" segments \
 ", unsigned long " flags ");"
 
-.\" FIXME(kexec_file_load):
-.\"     Why are the return types of kexec_load() and kexec_file_load()
-.\"     different?
-.BI "int kexec_file_load(int " kernel_fd ", int " initrd_fd ","
+.BI "long kexec_file_load(int " kernel_fd ", int " initrd_fd ","
 .br
 .BI "                    unsigned long " cmdline_len  \
 ", const char *" cmdline ","
@@ -207,8 +204,6 @@ The required constants are in the Linux kernel source file
 which is not currently exported to glibc.
 Therefore, these constants must be defined manually.
 
-.\" FIXME(kexec_file_load):
-.\" Is the following rationale accurate? Does it need expanding?
 The
 .BR kexec_file_load ()
 .\" See also http://lwn.net/Articles/603116/
@@ -224,8 +219,6 @@ The
 .BR kexec_file_load ()
 system call is available only if the kernel was configured with
 .BR CONFIG_KEXEC_FILE .
-.\" FIXME(kexec_file_load):
-.\"     Does kexec_file_load() need any other CONFIG_* options to be defined?
 .SH SEE ALSO
 .BR reboot (2),
 .BR syscall (2),