From: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-kernel@vger.kernel.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] regmap: debugfs: Add a registers `range' file
Date: Mon, 11 Feb 2013 13:46:21 +0000 [thread overview]
Message-ID: <20130211134621.GA14648@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20130211131641.GG4607@opensource.wolfsonmicro.com>
On Mon, Feb 11, 2013 at 01:16:41PM +0000, Mark Brown wrote:
> On Mon, Feb 11, 2013 at 10:52:23AM +0000, Dimitris Papastamos wrote:
>
> > +struct regmap_reg_range {
> > + unsigned int start;
> > + unsigned int end;
> > + unsigned int attr;
> > +};
>
> All we ever do with this struct is
>
> > + r.start = c->base_reg;
> > + r.end = c->max_reg;
> > + r.attr = c->reg_attr;
>
> pack it with the contents of a cache entry. Why not just use the cache
> entry directly?
Yea, will fix and re-send.
next prev parent reply other threads:[~2013-02-11 13:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 10:52 [PATCH] regmap: debugfs: Add a registers `range' file Dimitris Papastamos
2013-02-11 13:16 ` Mark Brown
2013-02-11 13:46 ` Dimitris Papastamos [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-30 13:50 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=20130211134621.GA14648@opensource.wolfsonmicro.com \
--to=dp@opensource.wolfsonmicro.com \
--cc=broonie@opensource.wolfsonmicro.com \
--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