From: Michael Ellerman <mpe@ellerman.id.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
kexec@lists.infradead.org, sourabhjain@linux.ibm.com,
bhe@redhat.com
Subject: Please add powerpc topic/kdump-hotplug branch to linux-next
Date: Tue, 23 Apr 2024 23:56:42 +1000 [thread overview]
Message-ID: <87bk60ji79.fsf@mail.lhotse> (raw)
Hi Stephen,
Can you please add the topic/kdump-hotplug branch of the powerpc tree to
linux-next. It contains a series that touches generic kexec code as well
as x86 and powerpc code.
The hope is to have to get it merged for v6.10, so it should go along
with the powerpc next branch in the merge order.
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/log/?h=topic/kdump-hotplug
cheers
next reply other threads:[~2024-04-23 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 13:56 Michael Ellerman [this message]
2024-04-23 21:40 ` Please add powerpc topic/kdump-hotplug branch to linux-next Stephen Rothwell
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=87bk60ji79.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=bhe@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sfr@canb.auug.org.au \
--cc=sourabhjain@linux.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 read-only IMAP folder(s) and NNTP newsgroup(s).