linux-kernel - Re: [PATCH 1/2] devicetree: mxsfb: add reset-active property

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAL_Jsq+jod-Jib8V1NYqBW2JQVrR+p3utHif=VknuEjdUh4BuA@mail.gmail.com>
Date:	Mon, 11 Jan 2016 18:28:31 -0600
From:	Rob Herring <robh@...nel.org>
To:	Måns Rullgård <mans@...sr.com>
Cc:	Pawel Moll <pawel.moll@....com>,
	Mark Rutland <mark.rutland@....com>,
	Ian Campbell <ijc+devicetree@...lion.org.uk>,
	Kumar Gala <galak@...eaurora.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Marek Vašut <marex@...x.de>
Subject: Re: [PATCH 1/2] devicetree: mxsfb: add reset-active property

On Mon, Jan 11, 2016 at 6:05 PM, Måns Rullgård <mans@...sr.com> wrote:
> Rob Herring <robh@...nel.org> writes:
>
>> On Mon, Jan 11, 2016 at 8:38 AM, Måns Rullgård <mans@...sr.com> wrote:
>>> Rob Herring <robh@...nel.org> writes:
>>>
>>>> On Tue, Dec 15, 2015 at 05:24:56PM +0000, Mans Rullgard wrote:
>>>>> Some boards connect the LCD_RESET pin to a reset input on the
>>>>> display panel.  On these boards, this pin must be set to the
>>>>> proper level for the display to function.
>>>>>
>>>>> This adds an optional "reset-active" property to the "display"
>>>>> subnode such that devicetrees can specify the desired polarity
>>>>> of the LCD_RESET pin.
>>>>>
>>>>> Signed-off-by: Mans Rullgard <mans@...sr.com>
>>>>
>>>> Acked-by: Rob Herring <robh@...nel.org>
>>>
>>> What happened to this patch?
>>
>> If I acked it, then I'm expecting the platform or subsystem maintainer
>> to pick up the series. I don't have patch #2 either, so I'm definitely
>> not picking up the series.
>
> Argh, get_maintainer.pl picking different people for different patches
> again.  I really wish it would/could send all patches in a series to the
> same recipients in cases like this.

Yeah, we really need some scripts around creating Cc list for series
gel_maintainers.pl really only works for a single commit. I imagine
everyone has some level of scripts around it.

> Should I resend both to the combined set of people so everybody gets to
> see everything?

Yes, as long as you are not resending daily, just resend. Send the
series TO who you think should merge it.

Rob