linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ldewangan@nvidia.com (Laxman Dewangan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] staging: iio: light: of: Fix vendor prefix of isl29018
Date: Tue, 17 Apr 2012 12:15:54 +0530	[thread overview]
Message-ID: <1334645155-13799-3-git-send-email-ldewangan@nvidia.com> (raw)
In-Reply-To: <1334645155-13799-1-git-send-email-ldewangan@nvidia.com>

ISL29018 is from Intersil Corporation and the vendor prefix
for this part should be "isl", at least not "invn" for OF
compatibility.

Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
---
 drivers/staging/iio/light/isl29018.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/staging/iio/light/isl29018.c b/drivers/staging/iio/light/isl29018.c
index 38ec52b..ee220ae 100644
--- a/drivers/staging/iio/light/isl29018.c
+++ b/drivers/staging/iio/light/isl29018.c
@@ -593,7 +593,7 @@ static const struct i2c_device_id isl29018_id[] = {
 MODULE_DEVICE_TABLE(i2c, isl29018_id);
 
 static const struct of_device_id isl29018_of_match[] = {
-	{ .compatible = "invn,isl29018", },
+	{ .compatible = "isl,isl29018", },
 	{ },
 };
 MODULE_DEVICE_TABLE(of, isl29018_of_match);
-- 
1.7.1.1

  parent reply	other threads:[~2012-04-17  6:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-17  6:45 [PATCH V1 0/3] ARM: dt: tegra: add ALS and proximity sensor ISL29018 Laxman Dewangan
2012-04-17  6:45 ` [PATCH 1/3] devicetree: Document Intersil Corporation vendor prefix Laxman Dewangan
2012-04-17  6:45 ` Laxman Dewangan [this message]
2012-04-17  7:15   ` [PATCH 2/3] staging: iio: light: of: Fix vendor prefix of isl29018 Jonathan Cameron
2012-04-17  6:45 ` [PATCH 3/3] ARM: dt: tegra_ventana: als and proximity sensor isl29018 support Laxman Dewangan
2012-04-17 22:35   ` Stephen Warren
2012-04-18  7:03     ` Laxman Dewangan
2012-04-19  9:12     ` Laxman Dewangan
2012-04-19 15:31       ` Stephen Warren
2012-04-24  7:42       ` Linus Walleij
2012-04-24 21:08     ` Olof Johansson

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=1334645155-13799-3-git-send-email-ldewangan@nvidia.com \
    --to=ldewangan@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.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).