From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: Dan Murphy <dmurphy@ti.com>,
robh+dt@kernel.org, pavel@ucw.cz, tony@atomide.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org
Subject: Re: [PATCH 3/4] mfd: ti-lmu: Remove LM3532 backlight driver references
Date: Mon, 25 Mar 2019 22:11:00 +0100 [thread overview]
Message-ID: <c950b7d3-eeb1-2dc2-b732-3a40d5b3a8b7@gmail.com> (raw)
In-Reply-To: <20190325075317.GW4731@dell>
On 3/25/19 8:53 AM, Lee Jones wrote:
> On Sat, 23 Mar 2019, Jacek Anaszewski wrote:
>
>> Hi Lee,
>>
>> Can we have your ack for this going via LED tree, please?
>
> Patch looks okay.
>
> You can take it through the LED, but if you do I will need you to send
> me a pull-request to a minimised immutable branch please.
>
> If you cannot do this, I can apply the set and provide the same to
> you.
>
> If you choose the former:
>
> Acked-for-MFD-by: Lee Jones <lee.jones@linaro.org>
>
> Please let me know what you decide
>
I've been exposing integration branches in the past, but after Linus'
message [0] I have my doubts now. I wonder if it wouldn't make more
sense if I just took the patches, and you'd cherry-pick them only in
case such a need occurs. This way we would avoid this whole merge
noise, which in an optimistic and very plausible case will not be needed
at all.
[0] https://lkml.org/lkml/2017/4/19/1104
--
Best regards,
Jacek Anaszewski
next prev parent reply other threads:[~2019-03-25 21:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 14:28 [PATCH 1/4] dt: lm3532: Add lm3532 dt doc and update ti_lmu doc Dan Murphy
2019-03-21 14:28 ` [PATCH 2/4] ARM: dts: omap4-droid4: Update backlight dt properties Dan Murphy
2019-04-04 0:03 ` Tony Lindgren
2019-04-04 20:12 ` Jacek Anaszewski
2019-04-04 22:00 ` Tony Lindgren
2019-04-07 18:31 ` Jacek Anaszewski
2019-03-21 14:28 ` [PATCH 3/4] mfd: ti-lmu: Remove LM3532 backlight driver references Dan Murphy
2019-03-23 16:47 ` Jacek Anaszewski
2019-03-25 7:53 ` Lee Jones
2019-03-25 21:11 ` Jacek Anaszewski [this message]
2019-04-03 7:57 ` Lee Jones
2019-04-03 17:45 ` Jacek Anaszewski
2019-04-04 2:44 ` Lee Jones
2019-04-04 0:04 ` Tony Lindgren
2019-03-21 14:28 ` [PATCH 4/4] leds: lm3532: Introduce the lm3532 LED driver Dan Murphy
2019-03-22 22:16 ` Tony Lindgren
2019-03-25 12:35 ` Dan Murphy
2019-03-25 14:54 ` Tony Lindgren
2019-03-25 16:01 ` Dan Murphy
2019-03-28 21:04 ` Sebastian Reichel
2019-04-03 20:06 ` Tony Lindgren
2019-04-03 23:55 ` Tony Lindgren
2019-04-04 0:09 ` Tony Lindgren
2019-04-04 18:48 ` Jacek Anaszewski
2019-04-04 19:23 ` Dan Murphy
2019-03-21 14:30 ` [PATCH 1/4] dt: lm3532: Add lm3532 dt doc and update ti_lmu doc Dan Murphy
2019-03-25 7:54 ` Lee Jones
2019-04-04 0:04 ` Tony Lindgren
2019-04-07 19:11 ` Jacek Anaszewski
-- strict thread matches above, loose matches on Subject: below --
2019-03-07 22:09 Dan Murphy
2019-03-07 22:09 ` [PATCH 3/4] mfd: ti-lmu: Remove LM3532 backlight driver references 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=c950b7d3-eeb1-2dc2-b732-3a40d5b3a8b7@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--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).