From: Lee Jones <lee.jones@linaro.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Jacek Anaszewski <j.anaszewski@samsung.com>,
linux-leds@vger.kernel.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
kyungmin.park@samsung.com, cooloney@gmail.com, rpurdie@rpsys.net,
sakari.ailus@iki.fi, s.nawrocki@samsung.com,
Andrzej Hajda <a.hajda@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>
Subject: Re: [PATCH/RFC v13 04/13] DT: Add documentation for the mfd Maxim max77693
Date: Mon, 23 Mar 2015 15:59:37 +0000 [thread overview]
Message-ID: <20150323155937.GQ24804@x1> (raw)
In-Reply-To: <20150323154807.GA13297@amd>
On Mon, 23 Mar 2015, Pavel Machek wrote:
> On Mon 2015-03-23 15:02:13, Lee Jones wrote:
> > On Mon, 23 Mar 2015, Pavel Machek wrote:
> > > On Mon 2015-03-23 12:07:43, Lee Jones wrote:
> > > > This patch requires a DT Ack.
> > >
> > > No, it requires DT people to be notified -- and they were, few times
> > > by now.
> > >
> > > They clearly don't care.
> >
> > Well fortunately for the Kernel community, I do care. And as this
> > patch adds 3 new DT properties, has been through many iterations
> > already with vast changes made over that period and there is still
> > some controversy looming, I'm saying that it _does_ require a DT
> > Ack.
>
> Can you help get that ack, then? As a maintainer, you have better
> chance getting reply from DT people than patch submitter.
Hopefully they will see my plea a couple of replies back.
If that fails I'll go poke them via other means. Failing that I'll go
see them in person and continually hit them with wet fish until one of
them relents.
--
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-03-23 15:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 15:45 [PATCH/RFC v13 00/13] LED / flash API integration Jacek Anaszewski
[not found] ` <1426175114-14876-1-git-send-email-j.anaszewski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-03-12 15:45 ` [PATCH/RFC v13 01/13] leds: flash: Fix the size of sysfs_groups array Jacek Anaszewski
2015-03-12 15:45 ` [PATCH/RFC v13 02/13] dt-binding: leds: Add common LED DT bindings macros Jacek Anaszewski
2015-03-18 1:33 ` Bryan Wu
2015-03-12 15:45 ` [PATCH/RFC v13 03/13] leds: Add support for max77693 mfd flash cell Jacek Anaszewski
2015-03-23 11:56 ` Lee Jones
2015-03-23 12:07 ` Lee Jones
2015-03-12 15:45 ` [PATCH/RFC v13 04/13] DT: Add documentation for the mfd Maxim max77693 Jacek Anaszewski
2015-03-23 12:07 ` Lee Jones
2015-03-23 14:22 ` Pavel Machek
2015-03-23 15:02 ` Lee Jones
2015-03-23 15:48 ` Pavel Machek
2015-03-23 15:59 ` Lee Jones [this message]
2015-03-23 18:28 ` Sylwester Nawrocki
2015-04-02 14:50 ` Pavel Machek
2015-04-02 19:33 ` Lee Jones
2015-03-12 15:45 ` [PATCH/RFC v13 05/13] leds: Add driver for AAT1290 current regulator Jacek Anaszewski
2015-03-12 15:45 ` [PATCH/RFC v13 06/13] of: Add Skyworks Solutions, Inc. vendor prefix Jacek Anaszewski
2015-03-12 15:45 ` [PATCH/RFC v13 07/13] DT: Add documentation for the Skyworks AAT1290 Jacek Anaszewski
2015-03-18 10:28 ` Jacek Anaszewski
2015-03-12 15:45 ` [PATCH/RFC v13 08/13] exynos4-is: Add support for v4l2-flash subdevs Jacek Anaszewski
2015-03-12 15:45 ` [PATCH/RFC v13 09/13] media: Add registration helpers for V4L2 flash sub-devices Jacek Anaszewski
2015-03-12 15:45 ` [PATCH/RFC v13 10/13] Documentation: leds: Add description of v4l2-flash sub-device Jacek Anaszewski
2015-03-18 12:39 ` Sakari Ailus
2015-03-18 14:36 ` Jacek Anaszewski
2015-03-12 15:45 ` [PATCH/RFC v13 11/13] DT: Add documentation for exynos4-is 'flashes' property Jacek Anaszewski
2015-03-12 15:45 ` [PATCH/RFC v13 12/13] leds: max77693: add support for V4L2 Flash sub-device Jacek Anaszewski
2015-03-12 15:45 ` [PATCH/RFC v13 13/13] leds: aat1290: " Jacek Anaszewski
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=20150323155937.GQ24804@x1 \
--to=lee.jones@linaro.org \
--cc=a.hajda@samsung.com \
--cc=cooloney@gmail.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=j.anaszewski@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rpurdie@rpsys.net \
--cc=s.nawrocki@samsung.com \
--cc=sakari.ailus@iki.fi \
/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).