linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dave Vasilevsky <dave@vasilevsky.ca>
To: glaubitz@physik.fu-berlin.de, bhe@redhat.com,
	linuxppc-dev@lists.ozlabs.org, linux-sh@vger.kernel.org,
	mpe@ellerman.id.au, 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: Sun, 8 Sep 2024 15:57:42 -0400	[thread overview]
Message-ID: <c04fe24a-26e6-44b5-a2dd-00eac589e36b@vasilevsky.ca> (raw)
In-Reply-To: <20240823125156.104775-1-dave@vasilevsky.ca>

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.

Thanks,
Dave


[0] http://patchwork.ozlabs.org/project/linuxppc-dev/patch/20240823125156.104775-1-dave@vasilevsky.ca/


  parent reply	other threads:[~2024-09-08 19:58 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 [this message]
2024-09-09  2:35   ` Baoquan He
2024-09-09  6:40   ` 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=c04fe24a-26e6-44b5-a2dd-00eac589e36b@vasilevsky.ca \
    --to=dave@vasilevsky.ca \
    --cc=Reimar.Doeffinger@gmx.de \
    --cc=bhe@redhat.com \
    --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 \
    --cc=mpe@ellerman.id.au \
    /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).