From: Samuel Ortiz <sameo@linux.intel.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
linux-kernel@vger.kernel.org,
patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] mfd: Convert pcf50633 to use new register map API
Date: Mon, 22 Aug 2011 11:10:27 +0200 [thread overview]
Message-ID: <20110822091027.GA8163@sortiz-mobl> (raw)
In-Reply-To: <20110822090313.GD4607@sortiz-mobl>
On Mon, Aug 22, 2011 at 11:03:13AM +0200, Samuel Ortiz wrote:
> Hi Lars,
>
> On Mon, Aug 08, 2011 at 05:29:27AM +0200, Lars-Peter Clausen wrote:
> >
> > > #include <linux/mfd/pcf50633/core.h>
> > >
> > [...]
> > > /* Read a block of up to 32 regs */
> > > int pcf50633_read_block(struct pcf50633 *pcf, u8 reg,
> > > int nr_regs, u8 *data)
> > > {
> > > - int ret;
> > > -
> > > - mutex_lock(&pcf->lock);
> > > - ret = __pcf50633_read(pcf, reg, nr_regs, data);
> > > - mutex_unlock(&pcf->lock);
> > > -
> > > - return ret;
> > > + return regmap_raw_read(pcf->regmap, reg, data, nr_regs);
> > > }
> > > EXPORT_SYMBOL_GPL(pcf50633_read_block);
> >
> > There are callers which expect pcf50633_read_block to return the number of
> > bytes read. We could change the wrapper to return nr_regs if regmap_raw_read
> > returns 0. But I guess it is best to just update the callers. Incremental patch
> > which does this at the end of the mail.
> I'd like to apply Mark's patch and yours. Could you please remove the
> unnecesary printk in your patch and I'll go ahead.
Nevermind, I just saw Mark's updated patch.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2011-08-22 9:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-06 3:45 [PATCH] mfd: Convert pcf50633 to use new register map API Mark Brown
2011-08-08 3:29 ` Lars-Peter Clausen
2011-08-08 5:07 ` Mark Brown
2011-08-22 9:03 ` Samuel Ortiz
2011-08-22 9:10 ` Samuel Ortiz [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-08-08 5:14 Mark Brown
2011-08-08 6:37 ` Lars-Peter Clausen
2011-08-08 8:04 Mark Brown
2011-08-10 4:21 ` Lars-Peter Clausen
2011-08-22 9:16 ` Samuel Ortiz
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=20110822091027.GA8163@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
/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