public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Cc: kexec@lists.infradead.org, ebiederm@xmission.com,
	Baoquan He <bhe@redhat.com>
Subject: [PATCH RESEND 0/4] Some minor cleanup patches resent
Date: Thu, 29 Sep 2022 12:29:32 +0800	[thread overview]
Message-ID: <20220929042936.22012-1-bhe@redhat.com> (raw)

These three patches are reviewed and acked, are all trivial clean up
patches.

And for the patch "kexec: replace crash_mem_range with range", I got a
ibm-p9wr ppc64le system to test, it works well.

Hi Andrew,

Please help pick them into mm-nonmm-unstable branch.


Chen Lifu (1):
  ARM: kexec: Make machine_crash_nonpanic_core() static

Jianglei Nie (1):
  proc/vmcore: fix potential memory leak in vmcore_init()

Li Chen (1):
  kexec: replace crash_mem_range with range

ye xingchen (1):
  kexec: Remove the unneeded result variable

 arch/arm/kernel/machine_kexec.c   |  2 +-
 arch/powerpc/kexec/file_load_64.c |  2 +-
 arch/powerpc/kexec/ranges.c       |  8 ++++----
 fs/proc/vmcore.c                  |  1 +
 include/linux/kexec.h             |  7 ++-----
 kernel/kexec_core.c               | 10 ++--------
 kernel/kexec_file.c               |  2 +-
 7 files changed, 12 insertions(+), 20 deletions(-)

-- 
2.34.1


             reply	other threads:[~2022-09-29  4:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-29  4:29 Baoquan He [this message]
2022-09-29  4:29 ` [PATCH RESEND 1/4] proc/vmcore: fix potential memory leak in vmcore_init() Baoquan He
2022-09-29  4:29 ` [PATCH RESEND 2/4] kexec: Remove the unneeded result variable Baoquan He
2022-09-29  4:29 ` [PATCH RESEND 3/4] kexec: replace crash_mem_range with range Baoquan He
2022-09-29  4:29 ` [PATCH RESEND 4/4] ARM: kexec: Make machine_crash_nonpanic_core() static 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=20220929042936.22012-1-bhe@redhat.com \
    --to=bhe@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.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