From: SF Markus Elfring <elfring@users.sourceforge.net>
To: linuxppc-dev@lists.ozlabs.org,
Anju T Sudhakar <anju@linux.vnet.ibm.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Bhumika Goyal <bhumirks@gmail.com>,
Corentin Labbe <clabbe.montjoie@gmail.com>,
Hemant Kumar <hemant@linux.vnet.ibm.com>,
Madhavan Srinivasan <maddy@linux.vnet.ibm.com>,
Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Michael Neuling <mikey@neuling.org>,
Neelesh Gupta <neelegup@linux.vnet.ibm.com>,
Nicholas Piggin <npiggin@gmail.com>,
Paul Mackerras <paulus@samba.org>, Rob Herring <robh@kernel.org>,
Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>,
Stewart Smith <stewart@linux.vnet.ibm.com>,
Tyrel Datwyler <tyreld@linux.vnet.ibm.com>,
Vasant Hegde <hegdevasant@linux.vnet.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: [PATCH 0/3] PowerPC-OPAL: Adjustments for some function implementations
Date: Tue, 17 Oct 2017 14:10:19 +0200 [thread overview]
Message-ID: <5fb4f314-cd23-c439-ab13-96b8188070e0@users.sourceforge.net> (raw)
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Tue, 17 Oct 2017 13:45:54 +0200
Three update suggestions were taken into account
from static source code analysis.
Markus Elfring (3):
Delete ten error messages for a failed memory allocation
Improve 12 size determinations
Fix a typo in a comment line of two file headers
arch/powerpc/platforms/powernv/opal-async.c | 2 --
arch/powerpc/platforms/powernv/opal-dump.c | 1 -
arch/powerpc/platforms/powernv/opal-flash.c | 8 +++----
arch/powerpc/platforms/powernv/opal-hmi.c | 9 ++++----
arch/powerpc/platforms/powernv/opal-imc.c | 10 ++++-----
.../powerpc/platforms/powernv/opal-memory-errors.c | 10 ++++-----
arch/powerpc/platforms/powernv/opal-psr.c | 2 +-
.../powerpc/platforms/powernv/opal-sensor-groups.c | 4 ++--
arch/powerpc/platforms/powernv/opal-sysparam.c | 25 +++++-----------------
arch/powerpc/platforms/powernv/opal-xscom.c | 2 +-
10 files changed, 25 insertions(+), 48 deletions(-)
--
2.14.2
next reply other threads:[~2017-10-17 12:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 12:10 SF Markus Elfring [this message]
2017-10-17 12:11 ` [PATCH 1/3] powerpc-opal: Delete ten error messages for a failed memory allocation SF Markus Elfring
2017-10-17 12:12 ` [PATCH 2/3] powerpc-opal: Improve 12 size determinations SF Markus Elfring
2017-10-17 12:14 ` [PATCH 3/3] powerpc-opal: Fix a typo in a comment line of two file headers SF Markus Elfring
2017-10-24 8:09 ` [3/3] " Michael Ellerman
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=5fb4f314-cd23-c439-ab13-96b8188070e0@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=anju@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=bhumirks@gmail.com \
--cc=clabbe.montjoie@gmail.com \
--cc=hegdevasant@linux.vnet.ibm.com \
--cc=hemant@linux.vnet.ibm.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.vnet.ibm.com \
--cc=mahesh@linux.vnet.ibm.com \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
--cc=neelegup@linux.vnet.ibm.com \
--cc=npiggin@gmail.com \
--cc=paulus@samba.org \
--cc=robh@kernel.org \
--cc=shilpa.bhat@linux.vnet.ibm.com \
--cc=stewart@linux.vnet.ibm.com \
--cc=tyreld@linux.vnet.ibm.com \
/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).