From: Mark Brown <broonie@kernel.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>,
cw00.choi@samsung.com, robh+dt@kernel.org, pawel.moll@arm.com,
mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
galak@codeaurora.org, myungjoo.ham@samsung.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH v2 4/5] mfd: arizona: Update DT binding documentation for mic detection
Date: Wed, 14 Oct 2015 10:49:03 +0100 [thread overview]
Message-ID: <20151014094903.GP14956@sirena.org.uk> (raw)
In-Reply-To: <20151014072812.GE32409@x1>
[-- Attachment #1: Type: text/plain, Size: 1311 bytes --]
On Wed, Oct 14, 2015 at 08:28:12AM +0100, Lee Jones wrote:
> On Tue, 13 Oct 2015, Mark Brown wrote:
> > On Tue, Oct 13, 2015 at 09:02:18AM +0100, Lee Jones wrote:
> > > Providing Acks should not (and has not to my knowledge) be a binding
> > > contract to continue providing Acks. However, should more bindings be
> > > submitted which appear as though they are related to a particular
> > > maintainer, then sure, you'll be asked for your expert eye again.
> > It's a bit concerning when it seems like my review is becoming a blocker
> > for something and I don't understand why.
> Not necessarily _your_ review. Just someone, other than the
> submitter, who I trust and knows about this stuff. You just happen
> to tick those boxes this time. Cross pollination and knowledge sharing
> is one of the characteristics of MLs which I'm particularly proud of.
That was what it read like.
> > When your power budget is in the low double digit microamps and you're
> > trying to respond promptly and reliably to rapidly changing and variable
> > physical inputs it gets complicated.
> This is exactly why I asked you.
> Thanks for adding structure to my PoV. ;)
So, a more specific question would have helped - just a general "any
thoughts" type question isn't very clear.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-10-14 9:49 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 16:29 [PATCH v2 0/5] Arizona Extcon Update Device Bindings Charles Keepax
2015-10-02 16:29 ` [PATCH v2 1/5] extcon: arizona: Add device binding to enable ADC mode micdet Charles Keepax
2015-10-02 16:29 ` [PATCH v2 2/5] extcon: arizona: Add device binding for the general purpose switch Charles Keepax
2015-10-02 16:29 ` [PATCH v2 3/5] extcon: arizona: Add device binding for jack detect polarity inversion Charles Keepax
2015-10-02 16:29 ` [PATCH v2 4/5] mfd: arizona: Update DT binding documentation for mic detection Charles Keepax
2015-10-05 10:02 ` Lee Jones
2015-10-07 10:00 ` Mark Brown
2015-10-07 12:26 ` Lee Jones
2015-10-12 8:45 ` Charles Keepax
2015-10-12 10:16 ` Chanwoo Choi
2015-10-12 10:25 ` Chanwoo Choi
2015-10-13 8:03 ` Lee Jones
2015-10-13 10:11 ` Chanwoo Choi
2015-10-12 13:43 ` Mark Brown
2015-10-13 8:02 ` Lee Jones
2015-10-13 12:14 ` Charles Keepax
2015-10-13 13:50 ` Lee Jones
2015-10-13 13:59 ` Chanwoo Choi
2015-10-13 14:09 ` Chanwoo Choi
2015-10-13 14:18 ` Lee Jones
2015-10-13 15:23 ` Charles Keepax
2015-10-13 15:12 ` Mark Brown
2015-10-14 7:28 ` Lee Jones
2015-10-14 9:49 ` Mark Brown [this message]
2015-10-14 12:30 ` Lee Jones
2015-10-14 13:09 ` Mark Brown
2015-10-14 13:20 ` Lee Jones
2015-10-13 8:08 ` Lee Jones
2015-10-13 12:15 ` Charles Keepax
2015-10-13 13:43 ` Lee Jones
2015-10-02 16:29 ` [PATCH v2 5/5] mfd: arizona: Update DT binding document for jack detection invert Charles Keepax
2015-10-05 10:01 ` Lee Jones
2015-10-12 8:15 ` Charles Keepax
2015-10-13 8:07 ` Lee Jones
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=20151014094903.GP14956@sirena.org.uk \
--to=broonie@kernel.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=myungjoo.ham@samsung.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@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).