From: Thiago Jung Bauermann <bauerman@linux.ibm.com>
To: Helge Deller <deller@gmx.de>
Cc: kexec@lists.infradead.org, Sven Schnelle <svens@stackframe.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v5 0/7] kexec: add generic support for elf kernel images
Date: Fri, 06 Sep 2019 18:47:35 -0300 [thread overview]
Message-ID: <87blvxgkqw.fsf@morokweng.localdomain> (raw)
In-Reply-To: <22b40bb7-6f86-0a69-12b2-12d90124173d@gmx.de>
Helge Deller <deller@gmx.de> writes:
> Hi all,
>
> This kexec patch series is the groundwork for kexec on the parisc architecture.
> Since we want kexec on parisc, I've applied it to my for-next-kexec tree [1],
> and can push it to Linus in the next merge window through the parisc tree [2].
I just had a look at this version and it looks fine to me. Identical to
the version I reviewed before except for the changes I suggested.
Thanks, Sven!
> If someone has any objections, or if you prefer to take it through
> a kexec or powerpc tree, please let me know.
>
> Helge
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git/log/?h=for-next-kexec
> [2] https://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git/log/?h=for-next
I noticed that the first patch is the only one that doesn't have my
Reviewed-by. If you want, you can add it:
Reviewed-by: Thiago Jung Bauermann <bauerman@linux.ibm.com>
If it's inconvenient to add it now since it's already applied, that's
fine too of course.
> On 23.08.19 21:49, Sven Schnelle wrote:
>> Changes to v4:
>> - rebase on current powerpc/merge tree
>> - fix syscall name in commit message
>> - remove a few unused #defines in arch/powerpc/kernel/kexec_elf_64.c
>>...
>> arch/Kconfig | 3 +
>> arch/powerpc/Kconfig | 1 +
>> arch/powerpc/kernel/kexec_elf_64.c | 545 +-----------------
>> include/linux/kexec.h | 23 +
>> kernel/Makefile | 1 +
>> .../kexec_elf_64.c => kernel/kexec_elf.c | 394 +++----------
>> 6 files changed, 115 insertions(+), 852 deletions(-)
>> copy arch/powerpc/kernel/kexec_elf_64.c => kernel/kexec_elf.c (50%)
--
Thiago Jung Bauermann
IBM Linux Technology Center
next prev parent reply other threads:[~2019-09-06 21:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 19:49 [PATCH v5 0/7] kexec: add generic support for elf kernel images Sven Schnelle
2019-08-23 19:49 ` [PATCH v5 1/7] kexec: add KEXEC_ELF Sven Schnelle
2019-08-23 19:49 ` [PATCH v5 2/7] kexec_elf: change order of elf_*_to_cpu() functions Sven Schnelle
2019-08-23 19:49 ` [PATCH v5 3/7] kexec_elf: remove parsing of section headers Sven Schnelle
2019-08-23 19:49 ` [PATCH v5 4/7] kexec_elf: remove PURGATORY_STACK_SIZE Sven Schnelle
2019-08-23 19:49 ` [PATCH v5 5/7] kexec_elf: remove Elf_Rel macro Sven Schnelle
2019-08-23 19:49 ` [PATCH v5 6/7] kexec_elf: remove unused variable in kexec_elf_load() Sven Schnelle
2019-08-23 19:49 ` [PATCH v5 7/7] kexec_elf: support 32 bit ELF files Sven Schnelle
2019-09-06 15:53 ` [PATCH v5 0/7] kexec: add generic support for elf kernel images Helge Deller
2019-09-06 21:47 ` Thiago Jung Bauermann [this message]
2019-09-06 22:01 ` Helge Deller
2019-09-07 1:34 ` Thiago Jung Bauermann
2019-09-09 8:20 ` Michael Ellerman
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=87blvxgkqw.fsf@morokweng.localdomain \
--to=bauerman@linux.ibm.com \
--cc=deller@gmx.de \
--cc=kexec@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=svens@stackframe.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;
as well as URLs for NNTP newsgroup(s).