From: SF Markus Elfring <elfring@users.sourceforge.net>
To: x86@kernel.org, "Andi Kleen" <ak@linux.intel.com>,
"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
"Borislav Petkov" <bp@suse.de>, "H. Peter Anvin" <hpa@zytor.com>,
"Ingo Molnar" <mingo@redhat.com>, "Jiri Olsa" <jolsa@redhat.com>,
"Jürgen Groß" <jgross@suse.com>,
"Len Brown" <len.brown@intel.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Thomas Gleixner" <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org,
Julia Lawall <julia.lawall@lip6.fr>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: [PATCH 0/4] x86/smpboot: Fine-tuning for smp_init_package_map()
Date: Mon, 5 Sep 2016 10:05:36 +0200 [thread overview]
Message-ID: <6dacb257-d15c-8ea1-9dd4-0440a5ecfd1d@users.sourceforge.net> (raw)
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Mon, 5 Sep 2016 09:50:05 +0200
A few update suggestions were taken into account
from static source code analysis.
Markus Elfring (4):
Use kmalloc_array()
Return directly after a failed kmalloc_array()
Replace one kzalloc() call by kcalloc()
Return directly after a failed kcalloc()
arch/x86/kernel/smpboot.c | 21 +++++++++++++++------
1 file changed, 15 insertions(+), 6 deletions(-)
--
2.9.3
next reply other threads:[~2016-09-05 8:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 8:05 SF Markus Elfring [this message]
2016-09-05 8:10 ` [PATCH 1/4] x86/smpboot: Use kmalloc_array() in smp_init_package_map() SF Markus Elfring
2016-09-05 9:19 ` Thomas Gleixner
2016-09-05 8:11 ` [PATCH 2/4] x86/smpboot: Return directly after a failed kmalloc_array() SF Markus Elfring
2016-09-05 8:12 ` [PATCH 3/4] x86/smpboot: Replace one kzalloc() call by kcalloc() SF Markus Elfring
2016-09-05 9:26 ` Paolo Bonzini
2016-09-05 9:29 ` Paolo Bonzini
2016-09-05 8:13 ` [PATCH 4/4] x86/smpboot: Return directly after a failed kcalloc() SF Markus Elfring
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=6dacb257-d15c-8ea1-9dd4-0440a5ecfd1d@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=ak@linux.intel.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=jolsa@redhat.com \
--cc=julia.lawall@lip6.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--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).