From: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
linux-kernel@vger.kernel.org, Liam Girdwood <lrg@ti.com>,
Graeme Gregory <gg@slimlogic.co.uk>,
Samuel Oritz <sameo@linux.intel.com>
Subject: Re: [PATCH 1/8] regmap: Introduce caching support
Date: Mon, 5 Sep 2011 10:44:39 +0100 [thread overview]
Message-ID: <20110905094439.GB30114@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110902234827.GA31813@opensource.wolfsonmicro.com>
On Sat, Sep 03, 2011 at 12:48:27AM +0100, Mark Brown wrote:
> On Fri, Sep 02, 2011 at 10:02:02PM +0200, Lars-Peter Clausen wrote:
> > On 09/02/2011 05:46 PM, Dimitris Papastamos wrote:
>
> > > +static const struct regcache_ops *cache_types[] = {
> > > +};
>
> > I wonder if it makes sense to keep a list of regcache_ops this way, or whether
> > it is not better to just pass the ops we want to use to regcache_init directly.
>
> Or have a function per cache type. I'm keen to hide the ops from users
> because I don't want to have to worry about them peering inside the
> internals.
Yes I guess I'll do that, sounds cleaner.
Thanks,
Dimitris
next prev parent reply other threads:[~2011-09-05 9:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 15:46 [PATCH 0/8] Introduce caching support for regmap Dimitris Papastamos
2011-09-02 15:46 ` [PATCH 1/8] regmap: Introduce caching support Dimitris Papastamos
2011-09-02 20:02 ` Lars-Peter Clausen
2011-09-02 23:48 ` Mark Brown
2011-09-03 1:10 ` Dimitris Papastamos
2011-09-04 15:57 ` Mark Brown
2011-09-05 9:44 ` Dimitris Papastamos [this message]
2011-09-05 9:43 ` Dimitris Papastamos
2011-09-05 9:55 ` Lars-Peter Clausen
2011-09-05 10:00 ` Dimitris Papastamos
2011-09-02 15:46 ` [PATCH 2/8] regmap: Add the indexed cache support Dimitris Papastamos
2011-09-02 20:16 ` Lars-Peter Clausen
2011-09-05 9:55 ` Dimitris Papastamos
2011-09-05 10:14 ` Lars-Peter Clausen
2011-09-05 18:22 ` Mark Brown
2012-07-17 11:16 ` Mark Brown
2012-07-17 14:24 ` Lars-Peter Clausen
2011-09-02 15:46 ` [PATCH 3/8] regmap: Add the rbtree " Dimitris Papastamos
2011-09-02 20:22 ` Lars-Peter Clausen
2011-09-05 9:58 ` Dimitris Papastamos
2011-09-02 15:46 ` [PATCH 4/8] regmap: Add the LZO " Dimitris Papastamos
2011-09-05 21:40 ` Matthieu CASTET
2011-09-07 19:19 ` Mark Brown
2011-09-02 15:46 ` [PATCH 5/8] regmap: Add the regcache_sync trace event Dimitris Papastamos
2011-09-02 15:46 ` [PATCH 6/8] regmap: Incorporate the regcache core into regmap Dimitris Papastamos
2011-09-02 15:46 ` [PATCH 7/8] regmap: It is impossible to be given a NULL defaults cache Dimitris Papastamos
2011-09-02 15:46 ` [PATCH 8/8] regmap: Support NULL cache_defaults_raw Dimitris Papastamos
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=20110905094439.GB30114@opensource.wolfsonmicro.com \
--to=dp@opensource.wolfsonmicro.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=gg@slimlogic.co.uk \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=sameo@linux.intel.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 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.