All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: Wang Jinchao <wangjinchao@xfusion.com>
Cc: akpm@linux-foundation.org, Vivek Goyal <vgoyal@redhat.com>,
	Dave Young <dyoung@redhat.com>,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	stone.xulei@xfusion.com
Subject: Re: [PATCH] crash_core: remove duplicated including of kexec.h
Date: Fri, 15 Dec 2023 17:09:01 +0800	[thread overview]
Message-ID: <ZXwXrU8YO1FC4A+W@MiWiFi-R3L-srv> (raw)
In-Reply-To: <202312151654+0800-wangjinchao@xfusion.com>

On 12/15/23 at 04:54pm, Wang Jinchao wrote:
> remove second include of linux/kexec.h

Good catch.

Acked-by: Baoquan He <bhe@redhat.com>

> 
> Signed-off-by: Wang Jinchao <wangjinchao@xfusion.com>
> ---
>  kernel/crash_core.c | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/kernel/crash_core.c b/kernel/crash_core.c
> index efe87d501c8c..d72985222b16 100644
> --- a/kernel/crash_core.c
> +++ b/kernel/crash_core.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.40.0
> 
> 
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
> 


_______________________________________________
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: Wang Jinchao <wangjinchao@xfusion.com>
Cc: akpm@linux-foundation.org, Vivek Goyal <vgoyal@redhat.com>,
	Dave Young <dyoung@redhat.com>,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	stone.xulei@xfusion.com
Subject: Re: [PATCH] crash_core: remove duplicated including of kexec.h
Date: Fri, 15 Dec 2023 17:09:01 +0800	[thread overview]
Message-ID: <ZXwXrU8YO1FC4A+W@MiWiFi-R3L-srv> (raw)
In-Reply-To: <202312151654+0800-wangjinchao@xfusion.com>

On 12/15/23 at 04:54pm, Wang Jinchao wrote:
> remove second include of linux/kexec.h

Good catch.

Acked-by: Baoquan He <bhe@redhat.com>

> 
> Signed-off-by: Wang Jinchao <wangjinchao@xfusion.com>
> ---
>  kernel/crash_core.c | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/kernel/crash_core.c b/kernel/crash_core.c
> index efe87d501c8c..d72985222b16 100644
> --- a/kernel/crash_core.c
> +++ b/kernel/crash_core.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.40.0
> 
> 
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
> 


  reply	other threads:[~2023-12-15  9:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-15  8:54 [PATCH] crash_core: remove duplicated including of kexec.h Wang Jinchao
2023-12-15  8:54 ` Wang Jinchao
2023-12-15  9:09 ` Baoquan He [this message]
2023-12-15  9:09   ` 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=ZXwXrU8YO1FC4A+W@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=stone.xulei@xfusion.com \
    --cc=vgoyal@redhat.com \
    --cc=wangjinchao@xfusion.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.