From: Liam Breck <liam@networkimprov.net>
To: "Andrew F. Davis" <afd@ti.com>, linux-pm@vger.kernel.org
Subject: [PATCH v12.7 0/10] bq27xxx_battery partial series
Date: Fri, 21 Apr 2017 02:59:52 -0700 [thread overview]
Message-ID: <20170421095959.14151-1-liam@networkimprov.net> (raw)
Latest changes (including 12.6):
Only DM update RAM chips by default
Add config_battery_bq27xxx_dt_updates_nvm. If defined, update NVM chips
and add module param dt_monitored_battery_updates_nvm
Fixed checkpatch errors and most warnings
Switched from -ENOSYS to -PERM, due to checkpatch warning
Add Copyright notice
unseal() returns error on key==0
Skip reset on non-cfgupdate chips if not updated
Emit warning if no dm_regs table
Map orig ID to chip ID via bq27xxx_chips[]
Drop "prototypes" in enum comments
Rename dupes detector bq27xxx_battery_dbg_regs_dupes()
^.^ ^.^ ^.^ - We has hungry for test!
next reply other threads:[~2017-04-21 9:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 9:59 Liam Breck [this message]
2017-04-21 9:59 ` [PATCH v12.7 03/10] power: power_supply: Add power_supply_battery_info and API Liam Breck
2017-04-21 9:59 ` [PATCH v12.7 05/10] power: bq27xxx_battery: Add bulk transfer bus methods Liam Breck
2017-04-21 9:59 ` [PATCH v12.7 06/10] power: bq27xxx_battery: Add chip data memory read/write support Liam Breck
2017-04-21 9:59 ` [PATCH v12.7 07/10] power: bq27xxx_battery: Add power_supply_battery_info support Liam Breck
2017-04-21 9:59 ` [PATCH v12.7 08/10] power: bq27xxx_battery: Enable data memory update for certain chips Liam Breck
2017-04-21 9:59 ` [PATCH v12.7 09/10] power: bq27xxx_battery: Flag identical register maps when in debug mode Liam Breck
2017-04-21 9:59 ` [PATCH v12.7 10/10] power: bq27xxx_battery: Remove duplicate register arrays Liam Breck
2017-05-01 15:22 ` [PATCH v12.7 0/10] bq27xxx_battery partial series Sebastian Reichel
2017-05-01 17:46 ` Liam Breck
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=20170421095959.14151-1-liam@networkimprov.net \
--to=liam@networkimprov.net \
--cc=afd@ti.com \
--cc=linux-pm@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;
as well as URLs for NNTP newsgroup(s).