From: Rob Herring <robh@kernel.org>
To: Jacek Anaszewski <jacek.anaszewski@gmail.com>
Cc: Dan Murphy <dmurphy@ti.com>, Pavel Machek <pavel@ucw.cz>,
lee.jones@linaro.org, tony@atomide.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org
Subject: Re: [PATCH v3 2/9] dt-bindings: ti-lmu: Remove LM3697
Date: Fri, 12 Oct 2018 11:26:19 -0500 [thread overview]
Message-ID: <20181012162619.GA28573@bogus> (raw)
In-Reply-To: <8c1559e1-b703-4c98-8bd9-7c9993bd59f5@gmail.com>
On Thu, Oct 11, 2018 at 09:38:53PM +0200, Jacek Anaszewski wrote:
> On 10/11/2018 08:34 PM, Dan Murphy wrote:
> > Pavel
> >
> > On 10/11/2018 01:27 PM, Pavel Machek wrote:
> >> On Thu 2018-10-11 11:51:16, Dan Murphy wrote:
> >>> Remove support for the LM3697 LED device
> >>> from the ti-lmu. The LM3697 will be supported
> >>> via a stand alone LED driver.
> >>>
> >>> Signed-off-by: Dan Murphy <dmurphy@ti.com>
> >>
> >> NAK.
> >
> > Thanks for the NAK.
> >
> > This NAK was NAK'd by other maintainer in the V2 RFC patchset
> >
> > https://lore.kernel.org/patchwork/patch/993171/
>
> I confirm. LM3697 is a standalone device and not a cell of any
> MFD device.
>
> Waiting for DT maintainer's ack.
You all sort out what you want... I can't follow it all, and I'm not
going to spend the time trying to figure out what is going on here.
As this is worded, changing the driver is a Linux problem and irrelevant
to the binding. Now if you want to move documentation to a location that
makes more sense, then fine. But structure patches that way and make it
clear that from an binding ABI perspective, nothing is changing.
Rob
next prev parent reply other threads:[~2018-10-12 16:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 16:51 [PATCH v3 0/9] TI LMU common Framework Dan Murphy
2018-10-11 16:51 ` [PATCH v3 1/9] leds: add TI LMU backlight driver Dan Murphy
2018-10-11 16:51 ` [PATCH v3 2/9] dt-bindings: ti-lmu: Remove LM3697 Dan Murphy
2018-10-11 18:27 ` Pavel Machek
2018-10-11 18:34 ` Dan Murphy
2018-10-11 19:38 ` Jacek Anaszewski
2018-10-12 16:26 ` Rob Herring [this message]
2018-10-12 18:03 ` Pavel Machek
2018-10-13 18:45 ` Jacek Anaszewski
2018-10-15 0:56 ` Rob Herring
2018-10-15 19:13 ` Jacek Anaszewski
2018-10-15 19:14 ` Dan Murphy
2018-10-15 21:45 ` Pavel Machek
2018-10-16 13:25 ` Dan Murphy
2018-10-18 22:10 ` Pavel Machek
2018-10-19 11:42 ` Dan Murphy
2018-10-19 14:58 ` Tony Lindgren
2018-10-24 8:55 ` Pavel Machek
2018-10-12 9:07 ` Lee Jones
2018-10-11 16:51 ` [PATCH v3 3/9] mfd: ti-lmu: Remove support for LM3697 Dan Murphy
2018-10-11 16:51 ` [PATCH v3 4/9] dt-bindings: leds: Add bindings for lm3697 driver Dan Murphy
2018-10-12 16:27 ` Rob Herring
2018-10-19 11:47 ` Dan Murphy
2018-10-11 16:51 ` [PATCH v3 5/9] leds: lm3697: Introduce the " Dan Murphy
2018-10-11 16:51 ` [PATCH v3 6/9] dt-bindings: ti-lmu: Remove LM3633 Dan Murphy
2018-10-11 16:51 ` [PATCH v3 7/9] mfd: ti-lmu: Remove support for LM3633 Dan Murphy
2018-10-11 16:51 ` [PATCH v3 8/9] dt-bindings: leds: Add support for the LM3633 Dan Murphy
2018-10-11 16:51 ` [PATCH v3 9/9] leds: lm3633: Introduce the lm3633 driver Dan Murphy
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=20181012162619.GA28573@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=tony@atomide.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).