From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762077AbcALAFn (ORCPT ); Mon, 11 Jan 2016 19:05:43 -0500 Received: from unicorn.mansr.com ([81.2.72.234]:57174 "EHLO unicorn.mansr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752518AbcALAFm convert rfc822-to-8bit (ORCPT ); Mon, 11 Jan 2016 19:05:42 -0500 From: =?iso-8859-1?Q?M=E5ns_Rullg=E5rd?= To: Rob Herring Cc: Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , "devicetree\@vger.kernel.org" , "linux-kernel\@vger.kernel.org" , Marek =?utf-8?Q?Va=C5=A1ut?= Subject: Re: [PATCH 1/2] devicetree: mxsfb: add reset-active property References: <1450200297-19243-1-git-send-email-mans@mansr.com> <20151220033823.GE9883@rob-hp-laptop> Date: Tue, 12 Jan 2016 00:05:33 +0000 In-Reply-To: (Rob Herring's message of "Mon, 11 Jan 2016 18:01:01 -0600") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Rob Herring writes: > On Mon, Jan 11, 2016 at 8:38 AM, Måns Rullgård wrote: >> Rob Herring 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 >>> >>> Acked-by: Rob Herring >> >> 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