From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: Baoquan He <bhe@redhat.com>,
kexec@lists.infradead.org, akpm@linux-foundation.org,
WANG Xuerui <kernel@xen0n.name>,
loongarch@lists.linux.dev
Subject: Re: [PATCH 1/2] arch/loongarch: clean up the left code and Kconfig item related to CRASH_CORE
Date: Wed, 17 Apr 2024 09:32:55 +0200 [thread overview]
Message-ID: <CAMuHMdVrFPJQ2B7-SBCq-m7tU9twKYwyH+0Czy-zB_n2F=VwrA@mail.gmail.com> (raw)
In-Reply-To: <CAAhV-H5xGDAkF2kjdveKoGd+GwYrmix8_E=YB0i=c98qOGvffw@mail.gmail.com>
On Wed, Apr 17, 2024 at 5:15 AM Huacai Chen <chenhuacai@kernel.org> wrote:
> On Sat, Mar 30, 2024 at 10:24 PM Baoquan He <bhe@redhat.com> wrote:
> >
> > On 03/30/24 at 09:59pm, Huacai Chen wrote:
> > > Queued, thanks.
> >
> > Thanks, Huacai. While I noticed Andrew has queued this patchset in his
> > mm-unstable branch.
> If I'm not mistaken, mm-unstable is target for the next 6.10, not for
> the current 6.9. But I think this patch should be a fix for 6.9, so I
> think it is more suitable in the loongarch-fixes branch. What's your
> opinion?
This would have been slightly more obvious with
Fixes: 85fcde402db191b5 ("kexec: split crashkernel reservation code
out from crash_core.c")
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2024-04-17 7:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 13:28 [PATCH 0/2] crash: clean up outdated codes and doc related to CRASH_CORE Baoquan He
2024-03-29 13:28 ` [PATCH 1/2] arch/loongarch: clean up the left code and Kconfig item " Baoquan He
2024-03-30 13:59 ` Huacai Chen
2024-03-30 14:23 ` Baoquan He
2024-04-17 3:14 ` Huacai Chen
2024-04-17 7:32 ` Geert Uytterhoeven [this message]
2024-03-29 13:28 ` [PATCH 2/2] Documentation: kdump: clean up the outdated description Baoquan He
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='CAMuHMdVrFPJQ2B7-SBCq-m7tU9twKYwyH+0Czy-zB_n2F=VwrA@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=chenhuacai@kernel.org \
--cc=kernel@xen0n.name \
--cc=kexec@lists.infradead.org \
--cc=loongarch@lists.linux.dev \
/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).