All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Ignat Korchagin <ignat@cloudflare.com>,
	linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org, linux-s390@vger.kernel.org,
	eric_devolder@yahoo.com, kernel-team <kernel-team@cloudflare.com>
Subject: Re: [PATCH 2/3] drivers/base/cpu: crash data showing should depends on KEXEC_CORE
Date: Sat, 25 Nov 2023 10:29:41 +0800	[thread overview]
Message-ID: <ZWFcFU9PjHl2L09u@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20231124084441.b913fc404fec53d5d0946c55@linux-foundation.org>

On 11/24/23 at 08:44am, Andrew Morton wrote:
> On Thu, 23 Nov 2023 19:15:43 +0800 Baoquan He <bhe@redhat.com> wrote:
> 
> > > > CONFIG_KEXEC is used to enable kexec_load interface, the
> > > > crash_notes/crash_notes_size/crash_hotplug showing depends on
> > > > CONFIG_KEXEC is incorrect. It should depend on KEXEC_CORE instead.
> > > >
> > > > Fix it now.
> > > 
> > > Can we add Fixes/CC stable, so it gets eventually backported into 6.6?
> > 
> > Makes sense. Will add it in v2 since I need respin to add the missing
> > stuff in patch 1. Thanks.
> 
> Please avoid mixing cc:stable patches and this-merge-window fixes in
> the same series as next-merge-window material.  Because I'll just have
> to separate them out anyway, causing what-I-merged to unnecessarily
> differ from what-you-sent.

Got it, will send them separately because the issue that this patch is fixing
has been there for very long time. Thanks for noticing.


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Ignat Korchagin <ignat@cloudflare.com>,
	linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org, linux-s390@vger.kernel.org,
	eric_devolder@yahoo.com, kernel-team <kernel-team@cloudflare.com>
Subject: Re: [PATCH 2/3] drivers/base/cpu: crash data showing should depends on KEXEC_CORE
Date: Sat, 25 Nov 2023 10:29:41 +0800	[thread overview]
Message-ID: <ZWFcFU9PjHl2L09u@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20231124084441.b913fc404fec53d5d0946c55@linux-foundation.org>

On 11/24/23 at 08:44am, Andrew Morton wrote:
> On Thu, 23 Nov 2023 19:15:43 +0800 Baoquan He <bhe@redhat.com> wrote:
> 
> > > > CONFIG_KEXEC is used to enable kexec_load interface, the
> > > > crash_notes/crash_notes_size/crash_hotplug showing depends on
> > > > CONFIG_KEXEC is incorrect. It should depend on KEXEC_CORE instead.
> > > >
> > > > Fix it now.
> > > 
> > > Can we add Fixes/CC stable, so it gets eventually backported into 6.6?
> > 
> > Makes sense. Will add it in v2 since I need respin to add the missing
> > stuff in patch 1. Thanks.
> 
> Please avoid mixing cc:stable patches and this-merge-window fixes in
> the same series as next-merge-window material.  Because I'll just have
> to separate them out anyway, causing what-I-merged to unnecessarily
> differ from what-you-sent.

Got it, will send them separately because the issue that this patch is fixing
has been there for very long time. Thanks for noticing.


WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Ignat Korchagin <ignat@cloudflare.com>,
	linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org, linux-s390@vger.kernel.org,
	eric_devolder@yahoo.com, kernel-team <kernel-team@cloudflare.com>
Subject: Re: [PATCH 2/3] drivers/base/cpu: crash data showing should depends on KEXEC_CORE
Date: Sat, 25 Nov 2023 10:29:41 +0800	[thread overview]
Message-ID: <ZWFcFU9PjHl2L09u@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20231124084441.b913fc404fec53d5d0946c55@linux-foundation.org>

On 11/24/23 at 08:44am, Andrew Morton wrote:
> On Thu, 23 Nov 2023 19:15:43 +0800 Baoquan He <bhe@redhat.com> wrote:
> 
> > > > CONFIG_KEXEC is used to enable kexec_load interface, the
> > > > crash_notes/crash_notes_size/crash_hotplug showing depends on
> > > > CONFIG_KEXEC is incorrect. It should depend on KEXEC_CORE instead.
> > > >
> > > > Fix it now.
> > > 
> > > Can we add Fixes/CC stable, so it gets eventually backported into 6.6?
> > 
> > Makes sense. Will add it in v2 since I need respin to add the missing
> > stuff in patch 1. Thanks.
> 
> Please avoid mixing cc:stable patches and this-merge-window fixes in
> the same series as next-merge-window material.  Because I'll just have
> to separate them out anyway, causing what-I-merged to unnecessarily
> differ from what-you-sent.

Got it, will send them separately because the issue that this patch is fixing
has been there for very long time. Thanks for noticing.


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-11-25  2:29 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-23  7:36 [PATCH 0/3] kernel/Kconfig.kexec: drop select of KEXEC for CRASH_DUMP Baoquan He
2023-11-23  7:36 ` Baoquan He
2023-11-23  7:36 ` Baoquan He
2023-11-23  7:36 ` [PATCH 1/3] " Baoquan He
2023-11-23  7:36   ` Baoquan He
2023-11-23  7:36   ` Baoquan He
2023-11-23  8:23   ` Ignat Korchagin
2023-11-23  8:23     ` Ignat Korchagin
2023-11-23  8:23     ` Ignat Korchagin
2023-11-23 11:07     ` Baoquan He
2023-11-23 11:07       ` Baoquan He
2023-11-23 11:07       ` Baoquan He
2023-11-23  7:36 ` [PATCH 2/3] drivers/base/cpu: crash data showing should depends on KEXEC_CORE Baoquan He
2023-11-23  7:36   ` Baoquan He
2023-11-23  7:36   ` Baoquan He
2023-11-23  8:34   ` Ignat Korchagin
2023-11-23  8:34     ` Ignat Korchagin
2023-11-23  8:34     ` Ignat Korchagin
2023-11-23 11:15     ` Baoquan He
2023-11-23 11:15       ` Baoquan He
2023-11-23 11:15       ` Baoquan He
2023-11-24 16:44       ` Andrew Morton
2023-11-24 16:44         ` Andrew Morton
2023-11-24 16:44         ` Andrew Morton
2023-11-25  2:29         ` Baoquan He [this message]
2023-11-25  2:29           ` Baoquan He
2023-11-25  2:29           ` Baoquan He
2023-11-23 14:13   ` Alexander Gordeev
2023-11-23 14:13     ` Alexander Gordeev
2023-11-23 14:13     ` Alexander Gordeev
2023-11-23 14:27     ` Baoquan He
2023-11-23 14:27       ` Baoquan He
2023-11-23 14:27       ` Baoquan He
2023-11-23  7:36 ` [PATCH 3/3] s390/Kconfig: drop select of KEXEC Baoquan He
2023-11-23  7:36   ` Baoquan He
2023-11-23  7:36   ` Baoquan He
2023-11-23 13:43   ` Alexander Gordeev
2023-11-23 13:43     ` Alexander Gordeev
2023-11-23 13:43     ` Alexander Gordeev
2023-11-23 14:31     ` Baoquan He
2023-11-23 14:31       ` Baoquan He
2023-11-23 14:31       ` Baoquan He
2023-11-26  0:07 ` [PATCH 0/3] kernel/Kconfig.kexec: drop select of KEXEC for CRASH_DUMP Eric DeVolder
2023-11-26  0:07   ` Eric DeVolder
2023-11-26  0:07   ` Eric DeVolder
2023-11-27  3:29   ` Baoquan He
2023-11-27  3:29     ` Baoquan He
2023-11-27  3:29     ` 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=ZWFcFU9PjHl2L09u@MiWiFi-R3L-srv \
    --to=bhe@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=eric_devolder@yahoo.com \
    --cc=ignat@cloudflare.com \
    --cc=kernel-team@cloudflare.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.