From: Baoquan He <bhe@redhat.com>
To: Thorsten Blum <thorsten.blum@toblux.com>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
David Howells <dhowells@redhat.com>,
Jeff Layton <jlayton@kernel.org>,
Miklos Szeredi <miklos@szeredi.hu>,
Amir Goldstein <amir73il@gmail.com>,
Vivek Goyal <vgoyal@redhat.com>, Dave Young <dyoung@redhat.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
netfs@lists.linux.dev, linux-fsdevel@vger.kernel.org,
linux-unionfs@vger.kernel.org, kexec@lists.infradead.org
Subject: Re: [PATCH 4/4] crash: Remove duplicate included header
Date: Sun, 5 May 2024 15:03:05 +0800 [thread overview]
Message-ID: <ZjcvKd+n74MFCJtj@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20240502212631.110175-4-thorsten.blum@toblux.com>
On 05/02/24 at 11:26pm, Thorsten Blum wrote:
> Remove duplicate included header file linux/kexec.h
>
> Signed-off-by: Thorsten Blum <thorsten.blum@toblux.com>
> ---
> kernel/crash_reserve.c | 1 -
> 1 file changed, 1 deletion(-)
Acked-by: Baoquan He <bhe@redhat.com>
>
> diff --git a/kernel/crash_reserve.c b/kernel/crash_reserve.c
> index 066668799f75..c460e687edd6 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.44.0
>
next prev parent reply other threads:[~2024-05-05 7:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 21:26 [PATCH 1/4] btrfs: Remove duplicate included header Thorsten Blum
2024-05-02 21:26 ` [PATCH 2/4] fscache: " Thorsten Blum
2024-05-02 21:26 ` [PATCH 3/4] overlayfs: " Thorsten Blum
2024-05-10 11:23 ` Miklos Szeredi
2024-05-02 21:26 ` [PATCH 4/4] crash: " Thorsten Blum
2024-05-05 7:03 ` Baoquan He [this message]
2024-05-02 22:50 ` [PATCH 1/4] btrfs: " David Sterba
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=ZjcvKd+n74MFCJtj@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=amir73il@gmail.com \
--cc=clm@fb.com \
--cc=dhowells@redhat.com \
--cc=dsterba@suse.com \
--cc=dyoung@redhat.com \
--cc=jlayton@kernel.org \
--cc=josef@toxicpanda.com \
--cc=kexec@lists.infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=netfs@lists.linux.dev \
--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 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).