From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,tglx@linutronix.de,mingo@redhat.com,jbohac@suse.cz,hpa@zytor.com,coxu@redhat.com,brgerst@gmail.com,bp@alien8.de,bhe@redhat.com,liaoyuanhong@vivo.com,akpm@linux-foundation.org
Subject: [merged mm-nonmm-stable] x86-crash-remove-redundant-0-value-initialization.patch removed from -mm tree
Date: Sat, 13 Sep 2025 17:35:20 -0700 [thread overview]
Message-ID: <20250914003521.2A108C4CEEB@smtp.kernel.org> (raw)
The quilt patch titled
Subject: x86/crash: remove redundant 0 value initialization
has been removed from the -mm tree. Its filename was
x86-crash-remove-redundant-0-value-initialization.patch
This patch was dropped because it was merged into the mm-nonmm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Liao Yuanhong <liaoyuanhong@vivo.com>
Subject: x86/crash: remove redundant 0 value initialization
Date: Mon, 18 Aug 2025 20:35:28 +0800
The crash_mem struct is already zeroed by vzalloc(). It's redundant to
initialize cmem->nr_ranges to 0.
Link: https://lkml.kernel.org/r/20250818123530.635234-1-liaoyuanhong@vivo.com
Signed-off-by: Liao Yuanhong <liaoyuanhong@vivo.com>
Cc: Baoquan He <bhe@redhat.com>
Cc: Borislav Betkov <bp@alien8.de>
Cc: Brian Gerst <brgerst@gmail.com>
Cc: Coiby Xu <coxu@redhat.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Jiri Bohac <jbohac@suse.cz>
Cc: Thomas Gleinxer <tglx@linutronix.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
arch/x86/kernel/crash.c | 2 --
1 file changed, 2 deletions(-)
--- a/arch/x86/kernel/crash.c~x86-crash-remove-redundant-0-value-initialization
+++ a/arch/x86/kernel/crash.c
@@ -172,7 +172,6 @@ static struct crash_mem *fill_up_crash_e
return NULL;
cmem->max_nr_ranges = nr_ranges;
- cmem->nr_ranges = 0;
return cmem;
}
@@ -332,7 +331,6 @@ int crash_setup_memmap_entries(struct ki
return -ENOMEM;
cmem->max_nr_ranges = nr_ranges;
- cmem->nr_ranges = 0;
memset(&cmd, 0, sizeof(struct crash_memmap_data));
cmd.params = params;
_
Patches currently in -mm which might be from liaoyuanhong@vivo.com are
reply other threads:[~2025-09-14 0:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250914003521.2A108C4CEEB@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=coxu@redhat.com \
--cc=hpa@zytor.com \
--cc=jbohac@suse.cz \
--cc=liaoyuanhong@vivo.com \
--cc=mingo@redhat.com \
--cc=mm-commits@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.