linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Olimpiu Dejeu <olimpiu@arcticsand.com>
Cc: lee.jones@linaro.org, linux-kernel@vger.kernel.org,
	linux-fbdev@vger.kernel.org, devicetree@vger.kernel.org,
	jg1.han@samsung.com
Subject: Re: [PATCH 2/2] backlight: arcxcnn: devicetree bindings for ArticSand devices
Date: Thu, 10 Nov 2016 13:25:58 -0600	[thread overview]
Message-ID: <20161110192558.ckyc6wv6mhsdousj@rob-hp-laptop> (raw)
In-Reply-To: <1478197768-3694-1-git-send-email-olimpiu@arcticsand.com>

On Thu, Nov 03, 2016 at 02:29:28PM -0400, Olimpiu Dejeu wrote:
> Resubmition of arcxcnn backliught driver addressing the naming convention

s/Resubmition/Re-submission/
s/backliught/backlight/

>  concerns raised by Rob H. Note that all the device tree properties are
>  determined by the board design or IC EPROM settings and are not intended
>  to be user adjustable.
> 
> Signed-off-by: Olimpiu Dejeu <olimpiu@arcticsand.com>
> 
> ---
>  .../bindings/leds/backlight/arcxcnn_bl.txt         | 31 ++++++++++++++++++++++
>  1 file changed, 31 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/leds/backlight/arcxcnn_bl.txt

With that,

Acked-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2016-11-10 19:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-03 18:29 [PATCH 2/2] backlight: arcxcnn: devicetree bindings for ArticSand devices Olimpiu Dejeu
2016-11-10 19:25 ` Rob Herring [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-11-18 15:17 Olimpiu Dejeu
2016-11-21 11:52 ` Lee Jones
2016-11-10 15:44 Olimpiu Dejeu
2016-11-11  8:45 ` Lee Jones
2016-10-26 20:30 Olimpiu Dejeu
2016-10-31  4:37 ` Rob Herring
2016-09-29 16:35 Olimpiu Dejeu
2016-09-29 19:21 ` Mark Rutland

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=20161110192558.ckyc6wv6mhsdousj@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jg1.han@samsung.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olimpiu@arcticsand.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).