"git am --skip" instead.
> To restore the original branch and stop patching, run "git am --abort".
>
> What is the order of your patch series of the three patchset?
>
> [PATCH v2 0/2] extend kexec_file_load system call
> [PATCH v5 00/13] kexec_file_loa
"git am --skip" instead.
> To restore the original branch and stop patching, run "git am --abort".
>
> What is the order of your patch series of the three patchset?
>
> [PATCH v2 0/2] extend kexec_file_load system call
> [PATCH v5 00/13] kexec_file_loa
t;.
What is the order of your patch series of the three patchset?
[PATCH v2 0/2] extend kexec_file_load system call
[PATCH v5 00/13] kexec_file_load implementation for PowerPC
[PATCH v2 0/6] kexec_file: Add buffer hand-over for the next kernel
Do they depend on other patches?
Thanks
Dave
t;.
What is the order of your patch series of the three patchset?
[PATCH v2 0/2] extend kexec_file_load system call
[PATCH v5 00/13] kexec_file_load implementation for PowerPC
[PATCH v2 0/6] kexec_file: Add buffer hand-over for the next kernel
Do they depend on other patches?
Thanks
Dave
Hello,
This patch series implements a mechanism which allows the kernel to pass
on a buffer to the kernel that will be kexec'd. This buffer is passed
as a segment which is added to the kimage when it is being prepared
by kexec_file_load.
How the second kernel is informed of this buffer is
Hello,
This patch series implements a mechanism which allows the kernel to pass
on a buffer to the kernel that will be kexec'd. This buffer is passed
as a segment which is added to the kimage when it is being prepared
by kexec_file_load.
How the second kernel is informed of this buffer is
6 matches
Mail list logo
