From: Jonathan Cameron <jic23@cam.ac.uk>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Current state of regmap.
Date: Mon, 05 Sep 2011 15:14:14 +0100 [thread overview]
Message-ID: <4E64D936.9030904@cam.ac.uk> (raw)
Hi Mark,
As my previous email said I've been messing around with regmap today.
I've run into a couple of bugs and was wondering if I'm running
behind the current version. I've pulled what is up on kernel.org
for linux-next at the moment.
As I'm emailing anyway. Everywhere other than regmap-debugfs max_register
is treated as the max valid. In there we have a loop that is
for (i = 0; i < map->max_register; i++) so that treats it as one
larger than the max valid register index.
Thanks,
Jonathan.
p.s. Nice work by the way.
next reply other threads:[~2011-09-05 14:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 14:14 Jonathan Cameron [this message]
2011-09-05 15:13 ` Current state of regmap 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=4E64D936.9030904@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.