From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: kexec@lists.infradead.org,
Linux Next Mailing List <linux-next@vger.kernel.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
bhe@redhat.com, sourabhjain@linux.ibm.com
Subject: Re: Please add powerpc topic/kdump-hotplug branch to linux-next
Date: Sun, 2 Jun 2024 15:20:58 +1000 [thread overview]
Message-ID: <20240602152058.276df8e9@canb.auug.org.au> (raw)
In-Reply-To: <87mso42pag.fsf@mail.lhotse>
[-- Attachment #1: Type: text/plain, Size: 845 bytes --]
Hi Michael,
On Sun, 02 Jun 2024 09:53:27 +1000 Michael Ellerman <mpe@ellerman.id.au> wrote:
>
> Stephen Rothwell <sfr@canb.auug.org.au> writes:
> >
> > On Tue, 23 Apr 2024 23:56:42 +1000 Michael Ellerman <mpe@ellerman.id.au> wrote:
> >>
> >> 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
> >
> > Added from today.
>
> This branch has now been merged and can be dropped from linux-next,
> thanks.
Removed.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2024-06-02 5:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 13:56 Please add powerpc topic/kdump-hotplug branch to linux-next Michael Ellerman
2024-04-23 21:40 ` Stephen Rothwell
2024-06-01 23:53 ` Michael Ellerman
2024-06-02 5:20 ` Stephen Rothwell [this message]
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=20240602152058.276df8e9@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=bhe@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.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 NNTP newsgroup(s).