From: Lianbo Jiang <lijiang@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
hpa@zytor.com, x86@kernel.org, bhe@redhat.com, dyoung@redhat.com,
jgross@suse.com, dhowells@redhat.com, Thomas.Lendacky@amd.com,
ebiederm@xmission.com, vgoyal@redhat.com,
kexec@lists.infradead.org
Subject: [PATCH 2/3 v3] x86/kdump cleanup: remove the unused crash_copy_backup_region()
Date: Sat, 12 Oct 2019 10:21:39 +0800 [thread overview]
Message-ID: <20191012022140.19003-3-lijiang@redhat.com> (raw)
In-Reply-To: <20191012022140.19003-1-lijiang@redhat.com>
The crash_copy_backup_region() has never been used, so clean
up the redundant code.
Signed-off-by: Lianbo Jiang <lijiang@redhat.com>
---
arch/x86/include/asm/crash.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/x86/include/asm/crash.h b/arch/x86/include/asm/crash.h
index 0acf5ee45a21..089b2850f9d1 100644
--- a/arch/x86/include/asm/crash.h
+++ b/arch/x86/include/asm/crash.h
@@ -3,7 +3,6 @@
#define _ASM_X86_CRASH_H
int crash_load_segments(struct kimage *image);
-int crash_copy_backup_region(struct kimage *image);
int crash_setup_memmap_entries(struct kimage *image,
struct boot_params *params);
void crash_smp_send_stop(void);
--
2.17.1
next prev parent reply other threads:[~2019-10-12 2:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-12 2:21 [PATCH 0/3 v3] x86/kdump: Fix 'kmem -s' reported an invalid freepointer when SME was active Lianbo Jiang
2019-10-12 2:21 ` [PATCH 1/3 " Lianbo Jiang
2019-10-12 2:21 ` Lianbo Jiang [this message]
2019-10-12 2:21 ` [PATCH 3/3 v3] x86/kdump: clean up all the code related to the backup region Lianbo Jiang
2019-10-12 11:26 ` Eric W. Biederman
2019-10-12 12:16 ` Dave Young
2019-10-13 3:54 ` Eric W. Biederman
2019-10-13 9:36 ` lijiang
2019-10-15 11:04 ` Eric W. Biederman
2019-10-16 8:40 ` lijiang
2019-10-16 14:30 ` lijiang
2019-10-16 16:51 ` Eric W. Biederman
2019-10-13 10:20 ` Dave Young
2019-10-14 10:02 ` lijiang
2019-10-15 11:11 ` Eric W. Biederman
2019-10-16 3:24 ` lijiang
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=20191012022140.19003-3-lijiang@redhat.com \
--to=lijiang@redhat.com \
--cc=Thomas.Lendacky@amd.com \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=dhowells@redhat.com \
--cc=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=vgoyal@redhat.com \
--cc=x86@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 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 NNTP newsgroup(s).