From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Pankaj Jangra <jangra.pankaj9@gmail.com>
Cc: Philip Rakity <philipspatches@gmail.com>,
linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org,
Philip Rakity <prakity@marvell.com>
Subject: Re: [PATCH 1/2] regulator: core.c Pass voltage to notifier when setting voltage
Date: Fri, 15 Jun 2012 19:08:12 +0100 [thread overview]
Message-ID: <20120615180812.GA18638@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CADTbHxq5rmHJtFTp53sYhFSYWVrSqyo_Jq+0aWNOF2HQR+nhGA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 550 bytes --]
On Fri, Jun 15, 2012 at 11:28:38PM +0530, Pankaj Jangra wrote:
> I am also curious to know if you pass the voltage here to notifier call
> how does it make any difference, since in
> blocking_notifier_call_chain() again passes the NULL. So does your patch
> should modify the arguments to this function also?
> Please let me know if i am missing something in understanding.
Your mail would have been rather more comprehensible if you'd mentioned
that you were talking about the call in _blocking_notifier_call_chain()
(which is obviously buggy).
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-06-15 18:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 22:06 [PATCH 1/2] regulator: core.c Pass voltage to notifier when setting voltage Philip Rakity
[not found] ` <CADTbHxq5rmHJtFTp53sYhFSYWVrSqyo_Jq+0aWNOF2HQR+nhGA@mail.gmail.com>
2012-06-15 18:08 ` Mark Brown [this message]
2012-06-15 18:29 ` Philip Rakity
2012-06-15 18:37 ` Pankaj Jangra
-- strict thread matches above, loose matches on Subject: below --
2012-06-15 18:27 Philip Rakity
2012-06-15 18:50 ` Pankaj Jangra
2012-06-15 19:18 ` Philip Rakity
2012-06-16 6:33 ` Pankaj Jangra
2012-06-17 18:12 ` 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=20120615180812.GA18638@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=jangra.pankaj9@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=philipspatches@gmail.com \
--cc=prakity@marvell.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.