From: mpa@pengutronix.de (Markus Pargmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] regmap: fixes
Date: Thu, 20 Aug 2015 11:12:31 +0200 [thread overview]
Message-ID: <1440061956-29064-1-git-send-email-mpa@pengutronix.de> (raw)
Hi,
These are some regmap fixes from the previous series
"Regmap max_raw_io and bmc150 SPI support". They are now splitted from the
other patches.
Changes in v2:
- Fixed free_context typo
- use_single_rw is now internally split into use_single_read/write
- Removed patches that wrongly tried to fix things
- Added simpler patches which check for the existence of bus->read/write to
avoid null dereferences
Best Regards,
Markus
Markus Pargmann (5):
regmap: Add missing comments about struct regmap_bus
regmap: Fix regmap_bulk_write for bus writes
regmap: Split use_single_rw internally into use_single_read/write
regmap: regmap_raw_read return error on !bus->read
regmap: No multi_write support if bus->write does not exist
drivers/base/regmap/internal.h | 6 ++++--
drivers/base/regmap/regcache.c | 2 +-
drivers/base/regmap/regmap-irq.c | 4 ++--
drivers/base/regmap/regmap.c | 31 ++++++++++++++++++++++++++-----
include/linux/regmap.h | 4 +++-
5 files changed, 36 insertions(+), 11 deletions(-)
--
2.4.6
next reply other threads:[~2015-08-20 9:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 9:12 Markus Pargmann [this message]
2015-08-20 9:12 ` [PATCH v2 1/5] regmap: Add missing comments about struct regmap_bus Markus Pargmann
2015-08-20 18:20 ` Mark Brown
2015-08-20 9:12 ` [PATCH v2 2/5] regmap: Fix regmap_bulk_write for bus writes Markus Pargmann
2015-08-20 18:27 ` Mark Brown
2015-08-20 9:12 ` [PATCH v2 3/5] regmap: Split use_single_rw internally into use_single_read/write Markus Pargmann
2015-08-20 18:28 ` Mark Brown
2015-08-20 9:12 ` [PATCH v2 4/5] regmap: regmap_raw_read return error on !bus->read Markus Pargmann
2015-08-20 18:30 ` Mark Brown
2015-08-20 9:12 ` [PATCH v2 5/5] regmap: No multi_write support if bus->write does not exist Markus Pargmann
2015-08-20 18:32 ` Mark Brown
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=1440061956-29064-1-git-send-email-mpa@pengutronix.de \
--to=mpa@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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).