From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: Dave Young <dyoung@redhat.com>, Baoquan He <bhe@redhat.com>,
Vivek Goyal <vgoyal@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-arm-kernel@lists.infradead.org, linux-ia64@vger.kernel.org,
linux-mips@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-riscv@lists.infradead.org, linux-sh@vger.kernel.org,
x86@kernel.org, linux-fsdevel@vger.kernel.org,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] kdump: simplify code
Date: Fri, 10 Dec 2021 21:35:59 +0800 [thread overview]
Message-ID: <1639143361-17773-1-git-send-email-yangtiezhu@loongson.cn> (raw)
Tiezhu Yang (2):
kdump: vmcore: move copy_to() from vmcore.c to uaccess.h
kdump: crashdump: use copy_to() to simplify the related code
arch/arm/kernel/crash_dump.c | 10 ++--------
arch/arm64/kernel/crash_dump.c | 10 ++--------
arch/ia64/kernel/crash_dump.c | 10 ++++------
arch/mips/kernel/crash_dump.c | 9 ++-------
arch/powerpc/kernel/crash_dump.c | 7 ++-----
arch/riscv/kernel/crash_dump.c | 9 ++-------
arch/sh/kernel/crash_dump.c | 9 ++-------
arch/x86/kernel/crash_dump_32.c | 9 ++-------
arch/x86/kernel/crash_dump_64.c | 9 ++-------
fs/proc/vmcore.c | 14 --------------
include/linux/uaccess.h | 14 ++++++++++++++
11 files changed, 34 insertions(+), 76 deletions(-)
--
2.1.0
next reply other threads:[~2021-12-10 13:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 13:35 Tiezhu Yang [this message]
2021-12-10 13:36 ` [PATCH 1/2] kdump: vmcore: move copy_to() from vmcore.c to uaccess.h Tiezhu Yang
2021-12-10 16:59 ` Andrew Morton
2021-12-10 23:50 ` Tiezhu Yang
2021-12-11 7:37 ` Christophe Leroy
2021-12-10 13:36 ` [PATCH 2/2] kdump: crashdump: use copy_to() to simplify the related code Tiezhu Yang
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=1639143361-17773-1-git-send-email-yangtiezhu@loongson.cn \
--to=yangtiezhu@loongson.cn \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=dyoung@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--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).