From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Kim, Milo" <Milo.Kim@ti.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] regmap-irq: use mask and val rather than using mask_buf_def
Date: Thu, 19 Jul 2012 10:10:12 +0100 [thread overview]
Message-ID: <20120719091011.GI4495@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <A874F61F95741C4A9BA573A70FE3998FD99F@DQHE02.ent.ti.com>
[-- Attachment #1: Type: text/plain, Size: 274 bytes --]
On Thu, Jul 19, 2012 at 09:04:39AM +0000, Kim, Milo wrote:
> Default mask value is used when updating irq registers.
> Rather than using mask_buf_def[], use mask and value explicitly.
Why? What is the problem you are seeing and what is the intended effect
of this change?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-07-19 9:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 9:04 [PATCH 1/2] regmap-irq: use mask and val rather than using mask_buf_def Kim, Milo
2012-07-19 9:10 ` Mark Brown [this message]
2012-07-20 7:08 ` Kim, Milo
2012-07-20 9:56 ` Mark Brown
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=20120719091011.GI4495@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Milo.Kim@ti.com \
--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;
as well as URLs for NNTP newsgroup(s).