devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Thompson <daniel.thompson@linaro.org>
To: Olimpiu Dejeu <olimpiu@arcticsand.com>, robh@kernel.org
Cc: lee.jones@linaro.org, linux-kernel@vger.kernel.org,
	linux-fbdev@vger.kernel.org, devicetree@vger.kernel.org,
	jingoohan1@gmail.com, bdodge@arcticsand.com, joe@perches.com,
	medasaro@arcticsand.com
Subject: Re: [PATCH v7 2/2] backlight arcxcnn add support for ArcticSand devices
Date: Tue, 14 Mar 2017 10:16:30 +0000	[thread overview]
Message-ID: <d628cdbc-dbc4-1065-23e8-63c0d6a2dd86@linaro.org> (raw)
In-Reply-To: <1489429323-6103-1-git-send-email-olimpiu@arcticsand.com>

On 13/03/17 18:22, Olimpiu Dejeu wrote:
> backlight: Add support for Arctic Sand LED backlight driver chips
> This driver provides support for the Arctic Sand arc2c0608 chip,
>     and provides a framework to support future devices.
> Signed-off-by: Olimpiu Dejeu <olimpiu@arcticsand.com>

Please could you also submit a patch to add arc to
./Documentation/devicetree/bindings/vendor-prefixes.txt.

checkpatch.pl should have been asking you to do since v1 but only if you 
test the patch series against a clean kernel (tools such as aiaiai can 
help with this).

However, once that is attended to:

Reviewed-by: Daniel Thompson <daniel.thompson@linaro.org>


Daniel.

  reply	other threads:[~2017-03-14 10:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-13 18:22 [PATCH v7 2/2] backlight arcxcnn add support for ArcticSand devices Olimpiu Dejeu
2017-03-14 10:16 ` Daniel Thompson [this message]
     [not found]   ` <d628cdbc-dbc4-1065-23e8-63c0d6a2dd86-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-03-14 11:27     ` Lee Jones
2017-03-14 15:53   ` Brian Dodge
     [not found]     ` <61f6e116-6190-72f3-ca89-54c9a94a6ac2-eV7fy4qpoLhpLGFMi4vTTA@public.gmane.org>
2017-03-14 16:08       ` Daniel Thompson

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=d628cdbc-dbc4-1065-23e8-63c0d6a2dd86@linaro.org \
    --to=daniel.thompson@linaro.org \
    --cc=bdodge@arcticsand.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jingoohan1@gmail.com \
    --cc=joe@perches.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=medasaro@arcticsand.com \
    --cc=olimpiu@arcticsand.com \
    --cc=robh@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).