From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: ciminaghi@gnudd.com
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] regmap: introduce tables for readable/writeable/volatile/precious checks
Date: Fri, 16 Nov 2012 10:19:07 +0900 [thread overview]
Message-ID: <20121116011904.GH4387@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1352983612-3474-1-git-send-email-ciminaghi@gnudd.com>
[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]
On Thu, Nov 15, 2012 at 01:46:52PM +0100, ciminaghi@gnudd.com wrote:
> I haven't seen any reply up to now, so I'm just resending the original patch
> (see https://lkml.org/lkml/2012/10/25/224).
> I just applied it to today's next and did a quick re-test.
The fact that you don't send a real name in your patch submission mails
might be an issue here - I suspect you've fallen foul of spam filtering,
either automatic or human, there's no sign of this in my pending queue.
> +static inline bool _reg_in_ranges(unsigned int reg,
> + const struct regmap_range *ranges,
> + unsigned int nranges)
> +{
> + const struct regmap_range *r;
> + int i;
> +
> + for (i = 0, r = ranges; i < nranges; i++, r++)
> + if (_reg_in_range(reg, r))
> + return true;
> + return false;
> +}
It would be better to make this an externally visible function (perhaps
just move it into the header with a regmap on the front of the name) so
that drivers can use this as part of the implementation of more complex
checks. Otherwise this looks fine.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-11-16 1:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 12:46 [PATCH RESEND] regmap: introduce tables for readable/writeable/volatile/precious checks ciminaghi
2012-11-16 1:19 ` Mark Brown [this message]
2012-11-16 23:53 ` Davide Ciminaghi
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=20121116011904.GH4387@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=ciminaghi@gnudd.com \
--cc=gregkh@linuxfoundation.org \
--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.