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 for Android: free password hash cracker in your pocket

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

Message-ID: <yw1xvb6zvf02.fsf@unicorn.mansr.com>
Date:	Tue, 12 Jan 2016 00:05:33 +0000
From:	Måns Rullgård <mans@...sr.com>
To:	Rob Herring <robh@...nel.org>
Cc:	Pawel Moll <pawel.moll@....com>,
	Mark Rutland <mark.rutland@....com>,
	Ian Campbell <ijc+devicetree@...lion.org.uk>,
	Kumar Gala <galak@...eaurora.org>,
	"devicetree\@vger.kernel.org" <devicetree@...r.kernel.org>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
	Marek Vašut <marex@...x.de>
Subject: Re: [PATCH 1/2] devicetree: mxsfb: add reset-active property

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.

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

-- 
Måns Rullgård