From: Rob Herring <robh@kernel.org>
To: "Måns Rullgård" <mans@mansr.com>
Cc: "Pawel Moll" <pawel.moll@arm.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
"Kumar Gala" <galak@codeaurora.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Marek Vašut" <marex@denx.de>
Subject: Re: [PATCH 1/2] devicetree: mxsfb: add reset-active property
Date: Mon, 11 Jan 2016 18:01:01 -0600 [thread overview]
Message-ID: <CAL_Jsq++UkEVJDcWVrDZ9pdkz++uU8uD_skYCAmGWv412RbnVA@mail.gmail.com> (raw)
In-Reply-To: <yw1xy4bww598.fsf@unicorn.mansr.com>
On Mon, Jan 11, 2016 at 8:38 AM, Måns Rullgård <mans@mansr.com> wrote:
> Rob Herring <robh@kernel.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@mansr.com>
>>
>> Acked-by: Rob Herring <robh@kernel.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.
Rob
next prev parent reply other threads:[~2016-01-12 0:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 17:24 [PATCH 1/2] devicetree: mxsfb: add reset-active property Mans Rullgard
2015-12-20 3:38 ` Rob Herring
2016-01-11 14:38 ` Måns Rullgård
2016-01-12 0:01 ` Rob Herring [this message]
[not found] ` <CAL_Jsq++UkEVJDcWVrDZ9pdkz++uU8uD_skYCAmGWv412RbnVA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-01-12 0:05 ` Måns Rullgård
2016-01-12 0:28 ` Rob Herring
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=CAL_Jsq++UkEVJDcWVrDZ9pdkz++uU8uD_skYCAmGWv412RbnVA@mail.gmail.com \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mans@mansr.com \
--cc=marex@denx.de \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.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).