From: Michael Ellerman <mpe@ellerman.id.au>
To: Dave Vasilevsky <dave@vasilevsky.ca>,
glaubitz@physik.fu-berlin.de, bhe@redhat.com,
linuxppc-dev@lists.ozlabs.org, linux-sh@vger.kernel.org,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: "Reimar Döffinger" <Reimar.Doeffinger@gmx.de>
Subject: Re: [PATCH] crash: Default to CRASH_DUMP=n when support for it is unlikely
Date: Mon, 09 Sep 2024 16:40:02 +1000 [thread overview]
Message-ID: <87ed5t49fh.fsf@mail.lhotse> (raw)
In-Reply-To: <c04fe24a-26e6-44b5-a2dd-00eac589e36b@vasilevsky.ca>
Dave Vasilevsky <dave@vasilevsky.ca> writes:
> I received a notification from Patchwork that my patch is now in the
> state "Handled Elsewhere".[0] Does that mean someone merged it
> somewhere? Or that I should be using a different mailing list? Or
> something else?
>
> I'd appreciate some guidance.
It was sent/Cc'ed to linuxppc-dev, so it was picked up by the linuxppc
patchwork, which is fine and normal.
Because it touches many arches I don't plan to merge it, I would expect
the kexec maintainers to take it.
So I marked it as "Handled Elsewhere" in the linuxppc patchwork - ie.
not handled via the powerpc tree.
That doesn't mean anyone else has merged it, it just means I haven't and
don't plan to.
cheers
prev parent reply other threads:[~2024-09-09 6:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 12:51 [PATCH] crash: Default to CRASH_DUMP=n when support for it is unlikely Dave Vasilevsky
2024-08-23 13:13 ` Geert Uytterhoeven
2024-08-23 18:16 ` John Paul Adrian Glaubitz
2024-08-27 6:22 ` Baoquan He
2024-08-27 6:37 ` John Paul Adrian Glaubitz
2024-08-27 9:01 ` Baoquan He
2024-08-26 2:02 ` Michael Ellerman
2024-08-26 5:38 ` John Paul Adrian Glaubitz
2024-08-26 6:03 ` Dave Vasilevsky
2024-08-30 3:15 ` Baoquan He
2024-08-30 3:37 ` Dave Vasilevsky
2024-08-30 6:30 ` Baoquan He
2024-08-30 6:35 ` Baoquan He
2024-08-30 7:24 ` Dave Vasilevsky
2024-09-08 19:57 ` Dave Vasilevsky
2024-09-09 2:35 ` Baoquan He
2024-09-09 6:40 ` Michael Ellerman [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=87ed5t49fh.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=Reimar.Doeffinger@gmx.de \
--cc=bhe@redhat.com \
--cc=dave@vasilevsky.ca \
--cc=glaubitz@physik.fu-berlin.de \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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).