From: mpa@pengutronix.de (Markus Pargmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/4] regmap: fixes
Date: Fri, 21 Aug 2015 10:26:39 +0200 [thread overview]
Message-ID: <1440145603-9612-1-git-send-email-mpa@pengutronix.de> (raw)
Hi,
I changed the comments you mentioned in your review. I hope they are better
to understand now.
Best Regards,
Markus
Changes in v3:
- Change comments in patch 1 'regmap: Add missing comments about struct regmap_bus'
- Change description in patch 2 'regmap: Fix regmap_bulk_write for bus writes'
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
Markus Pargmann (4):
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: 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 | 30 ++++++++++++++++++++++++------
include/linux/regmap.h | 5 ++++-
5 files changed, 35 insertions(+), 12 deletions(-)
--
2.4.6
next reply other threads:[~2015-08-21 8:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 8:26 Markus Pargmann [this message]
2015-08-21 8:26 ` [PATCH v3 1/4] regmap: Add missing comments about struct regmap_bus Markus Pargmann
2015-08-21 8:26 ` [PATCH v3 2/4] regmap: Fix regmap_bulk_write for bus writes Markus Pargmann
2015-08-21 8:26 ` [PATCH v3 3/4] regmap: Split use_single_rw internally into use_single_read/write Markus Pargmann
2015-08-21 8:26 ` [PATCH v3 4/4] regmap: No multi_write support if bus->write does not exist Markus Pargmann
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=1440145603-9612-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).