From: Lee Jones <lee.jones@linaro.org>
To: Chanwoo Choi <cw00.choi@samsung.com>
Cc: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>,
broonie@kernel.org, myungjoo.ham@samsung.com,
lgirdwood@gmail.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH v3 3/4] mfd: arizona: Remove bindings covered in new subsystem specific docs
Date: Wed, 28 Oct 2015 09:17:39 +0000 [thread overview]
Message-ID: <20151028091739.GL5828@x1> (raw)
In-Reply-To: <5630912A.9090601@samsung.com>
On Wed, 28 Oct 2015, Chanwoo Choi wrote:
> On 2015년 10월 28일 18:03, Lee Jones wrote:
> > On Tue, 27 Oct 2015, Charles Keepax wrote:
> >
> >> Binding documentation has been added in new subsystem specific binding
> >> documents. This patch removes the now duplicate documentation from the
> >> MFD documentation.
> >>
> >> Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> >> ---
> >>
> >> Changes since v2:
> >> - No longer moving the core regulators into the regulator binding document,
> >> as they are properties of the device as a whole not just the regulators
> >> - Moved the maintainer updates into a seperate patch
> >>
> >> Lee, I have removed your ack because the patch has changed a fair amount.
> >> Apologies if this would not have been your preference.
> >
> > That was the right thing to do.
> >
> >> Thanks,
> >> Charles
> >>
> >> Documentation/devicetree/bindings/mfd/arizona.txt | 15 +++------------
> >> 1 files changed, 3 insertions(+), 12 deletions(-)
> >
> > Applied, thanks.
>
> If you possible, could you pick patch1[1] which has already the acked tag of me?
> [1] [PATCH v3 1/4] extcon: arizona: Add extcon specific device tree binding document
Yes, no problem.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2015-10-28 9:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 16:01 [PATCH v3 1/4] extcon: arizona: Add extcon specific device tree binding document Charles Keepax
2015-10-27 16:01 ` [PATCH v3 2/4] regulator: arizona: Add regulator " Charles Keepax
2015-10-27 16:01 ` [PATCH v3 3/4] mfd: arizona: Remove bindings covered in new subsystem specific docs Charles Keepax
2015-10-28 9:03 ` Lee Jones
2015-10-28 9:11 ` Chanwoo Choi
2015-10-28 9:17 ` Lee Jones [this message]
[not found] ` <1445961719-1020-1-git-send-email-ckeepax-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2015-10-27 16:01 ` [PATCH v3 4/4] MAINTAINERS: Add binding docs for Cirrus Logic/Wolfson Arizona devices Charles Keepax
[not found] ` <1445961719-1020-4-git-send-email-ckeepax-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2015-10-28 9:01 ` Lee Jones
2015-10-28 9:03 ` Lee Jones
2015-10-28 9:04 ` Chanwoo Choi
[not found] ` <56308FB4.8010707-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-10-28 9:18 ` Lee Jones
2015-10-28 9:19 ` [PATCH v3 1/4] extcon: arizona: Add extcon specific device tree binding document 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=20151028091739.GL5828@x1 \
--to=lee.jones@linaro.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--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;
as well as URLs for NNTP newsgroup(s).