From: Baoquan He <bhe@redhat.com>
To: Thorsten Blum <thorsten.blum@toblux.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
vgoyal@redhat.com, dyoung@redhat.com, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH] crash: Remove duplicate included header
Date: Wed, 3 Jul 2024 19:24:09 +0800 [thread overview]
Message-ID: <ZoU02QtQZ46pmE9/@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20240703093517.730559-2-thorsten.blum@toblux.com>
Hi,
On 07/03/24 at 11:35am, Thorsten Blum wrote:
> Remove duplicate included header file linux/kexec.h
>
> Acked-by: Baoquan He <bhe@redhat.com>
> Signed-off-by: Thorsten Blum <thorsten.blum@toblux.com>
> ---
> kernel/crash_reserve.c | 1 -
> 1 file changed, 1 deletion(-)
Thanks for catching this, while,
It has been fixed by below patch in next tree:
commit 5eb1911a8c63f0e10a5f746f52fcc3c9bbfbc710
Author: Wenchao Hao <haowenchao22@gmail.com>
Date: Thu Jun 6 17:14:27 2024 +0800
crash: remove header files which are included more than once
>
> diff --git a/kernel/crash_reserve.c b/kernel/crash_reserve.c
> index 5b2722a93a48..d3b4cd12bdd1 100644
> --- a/kernel/crash_reserve.c
> +++ b/kernel/crash_reserve.c
> @@ -13,7 +13,6 @@
> #include <linux/memory.h>
> #include <linux/cpuhotplug.h>
> #include <linux/memblock.h>
> -#include <linux/kexec.h>
> #include <linux/kmemleak.h>
>
> #include <asm/page.h>
> --
> 2.45.2
>
_______________________________________________
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: Thorsten Blum <thorsten.blum@toblux.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
vgoyal@redhat.com, dyoung@redhat.com, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH] crash: Remove duplicate included header
Date: Wed, 3 Jul 2024 19:24:09 +0800 [thread overview]
Message-ID: <ZoU02QtQZ46pmE9/@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20240703093517.730559-2-thorsten.blum@toblux.com>
Hi,
On 07/03/24 at 11:35am, Thorsten Blum wrote:
> Remove duplicate included header file linux/kexec.h
>
> Acked-by: Baoquan He <bhe@redhat.com>
> Signed-off-by: Thorsten Blum <thorsten.blum@toblux.com>
> ---
> kernel/crash_reserve.c | 1 -
> 1 file changed, 1 deletion(-)
Thanks for catching this, while,
It has been fixed by below patch in next tree:
commit 5eb1911a8c63f0e10a5f746f52fcc3c9bbfbc710
Author: Wenchao Hao <haowenchao22@gmail.com>
Date: Thu Jun 6 17:14:27 2024 +0800
crash: remove header files which are included more than once
>
> diff --git a/kernel/crash_reserve.c b/kernel/crash_reserve.c
> index 5b2722a93a48..d3b4cd12bdd1 100644
> --- a/kernel/crash_reserve.c
> +++ b/kernel/crash_reserve.c
> @@ -13,7 +13,6 @@
> #include <linux/memory.h>
> #include <linux/cpuhotplug.h>
> #include <linux/memblock.h>
> -#include <linux/kexec.h>
> #include <linux/kmemleak.h>
>
> #include <asm/page.h>
> --
> 2.45.2
>
next prev parent reply other threads:[~2024-07-03 11:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 9:35 [RESEND PATCH] crash: Remove duplicate included header Thorsten Blum
2024-07-03 9:35 ` Thorsten Blum
2024-07-03 11:24 ` Baoquan He [this message]
2024-07-03 11:24 ` 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=ZoU02QtQZ46pmE9/@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dyoung@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thorsten.blum@toblux.com \
--cc=vgoyal@redhat.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 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.