From: SF Markus Elfring <elfring@users.sourceforge.net>
To: linux-pm@vger.kernel.org, Sebastian Reichel <sre@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: [PATCH 0/2] max8997_charger: Fine-tuning for max8997_battery_probe()
Date: Mon, 30 Oct 2017 22:34:27 +0100 [thread overview]
Message-ID: <286b1fea-ccff-5fed-5e2d-fc3b0064cd4d@users.sourceforge.net> (raw)
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Mon, 30 Oct 2017 22:30:22 +0100
Two update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Use common error handling code
Improve a size determination
drivers/power/supply/max8997_charger.c | 19 +++++++++----------
1 file changed, 9 insertions(+), 10 deletions(-)
--
2.14.3
next reply other threads:[~2017-10-30 21:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 21:34 SF Markus Elfring [this message]
2017-10-30 21:35 ` [PATCH 1/2] max8997_charger: Use common error handling code in max8997_battery_probe() SF Markus Elfring
2017-10-30 21:36 ` [PATCH 2/2] max8997_charger: Improve a size determination " 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=286b1fea-ccff-5fed-5e2d-fc3b0064cd4d@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=sre@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).