linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Lee Jones <lee.jones@linaro.org>,
	Daniel Thompson <daniel.thompson@linaro.org>,
	Jingoo Han <jingoohan1@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
	Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH 1/2 v2] backlight: gpio: Convert to use GPIO descriptor
Date: Tue, 1 Aug 2017 10:20:32 +0200	[thread overview]
Message-ID: <CACRpkdaCXgp+kZGpPhCR2yR3xLMMRs1NnySg0HkB=Je9EVimiQ@mail.gmail.com> (raw)
In-Reply-To: <20170530114822.24308-1-linus.walleij@linaro.org>

On Tue, May 30, 2017 at 1:48 PM, Linus Walleij <linus.walleij@linaro.org> wrote:

> This driver is predominantly used by device tree systems, all
> of which can deal with modern GPIO descriptors. The legacy
> GPIO API is only used by one SH board so make the GPIO
> descriptor the default way to deal with it.
>
> As an intended side effect we do not need to look around in
> the device tree for the inversion flag since the GPIO
> descriptors will intrinsically deal with this.
>
> Acked-by: Daniel Thompson <daniel.thompson@linaro.org>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> ChangeLog v1->v2:
> - Assign flags value using the ternary operator.

This patch seems to have been inadvertedly dropped?

Can it be applied, along with 2/2?

Yours,
Linus Walleij

  parent reply	other threads:[~2017-08-01  8:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-30 11:48 [PATCH 1/2 v2] backlight: gpio: Convert to use GPIO descriptor Linus Walleij
2017-05-30 11:48 ` [PATCH 2/2 v2] backlight: gpio: delete pdata inversion Linus Walleij
2017-08-01 10:28   ` Laurent Pinchart
2017-08-07 16:12   ` Lee Jones
2017-08-01  8:20 ` Linus Walleij [this message]
2017-08-01 10:29   ` [PATCH 1/2 v2] backlight: gpio: Convert to use GPIO descriptor Laurent Pinchart
2017-08-07  7:53   ` Lee Jones
2017-08-07 16:12 ` Lee Jones

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='CACRpkdaCXgp+kZGpPhCR2yR3xLMMRs1NnySg0HkB=Je9EVimiQ@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=daniel.thompson@linaro.org \
    --cc=jingoohan1@gmail.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    /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).