From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Current state of regmap.
Date: Mon, 5 Sep 2011 08:13:13 -0700 [thread overview]
Message-ID: <20110905151312.GC3889@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4E64D936.9030904@cam.ac.uk>
On Mon, Sep 05, 2011 at 03:14:14PM +0100, Jonathan Cameron wrote:
> 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.
That's the current state, I'm running development systems here where all
the I2C and SPI devices on the system go through regmap and anyone
running ASoC will be using it. Though there's a few patches floating
around now and I'm just testing the module_put() fix so it'll not be the
current state soonish. kernel.org is closed for updates right now, if I
do much i'll probably show up on opensource.wolfsonmicro.com in the
short term.
> 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.
That's an off by one in the debugfs code, will fix. You can check this
sort of stuff out by looking at the users.
prev parent reply other threads:[~2011-09-05 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 14:14 Current state of regmap Jonathan Cameron
2011-09-05 15:13 ` Mark Brown [this message]
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=20110905151312.GC3889@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=jic23@cam.ac.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox