From: Jonathan Cameron <jic23@cam.ac.uk> To: Laxman Dewangan <ldewangan@nvidia.com> Cc: grant.likely@secretlab.ca, rob.herring@calxeda.com, rdunlap@xenotime.net, linux@arm.linux.org.uk, gregkh@linuxfoundation.org, broonie@opensource.wolfsonmicro.com, swarren@nvidia.com, cbouatmailru@gmail.com, olof@lixom.net, linus.walleij@linaro.org, lars@metafoo.de, bfreed@chromium.org, grundler@chromium.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-iio@vger.kernel.org, devel@driverdev.osuosl.org Subject: Re: [PATCH 2/3] staging: iio: light: of: Fix vendor prefix of isl29018 Date: Tue, 17 Apr 2012 08:15:44 +0100 [thread overview] Message-ID: <4F8D18A0.9030108@cam.ac.uk> (raw) In-Reply-To: <1334645155-13799-3-git-send-email-ldewangan@nvidia.com> On 4/17/2012 7:45 AM, Laxman Dewangan wrote: > ISL29018 is from Intersil Corporation and the vendor prefix > for this part should be "isl", at least not "invn" for OF > compatibility. Fine with me. Not really my domain other than where it sits though! Send on to Greg when you get acks from device tree side. > > Signed-off-by: Laxman Dewangan<ldewangan@nvidia.com> Acked-by: Jonathan Cameron <jic23@kernel.org> > --- > 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);
WARNING: multiple messages have this Message-ID (diff)
From: jic23@cam.ac.uk (Jonathan Cameron) 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 08:15:44 +0100 [thread overview] Message-ID: <4F8D18A0.9030108@cam.ac.uk> (raw) In-Reply-To: <1334645155-13799-3-git-send-email-ldewangan@nvidia.com> On 4/17/2012 7:45 AM, Laxman Dewangan wrote: > ISL29018 is from Intersil Corporation and the vendor prefix > for this part should be "isl", at least not "invn" for OF > compatibility. Fine with me. Not really my domain other than where it sits though! Send on to Greg when you get acks from device tree side. > > Signed-off-by: Laxman Dewangan<ldewangan@nvidia.com> Acked-by: Jonathan Cameron <jic23@kernel.org> > --- > 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);
next prev parent reply other threads:[~2012-04-17 7:15 UTC|newest] Thread overview: 30+ 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 ` 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 2012-04-17 6:45 ` [PATCH 2/3] staging: iio: light: of: Fix vendor prefix of isl29018 Laxman Dewangan 2012-04-17 6:45 ` Laxman Dewangan 2012-04-17 7:15 ` Jonathan Cameron [this message] 2012-04-17 7:15 ` 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 6:45 ` Laxman Dewangan [not found] ` <1334645155-13799-4-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> 2012-04-17 22:35 ` Stephen Warren 2012-04-17 22:35 ` Stephen Warren 2012-04-17 22:35 ` Stephen Warren [not found] ` <4F8DF01D.9040900-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org> 2012-04-18 7:03 ` Laxman Dewangan 2012-04-18 7:03 ` Laxman Dewangan 2012-04-18 7:03 ` Laxman Dewangan 2012-04-18 7:03 ` Laxman Dewangan 2012-04-19 9:12 ` Laxman Dewangan 2012-04-19 9:12 ` Laxman Dewangan 2012-04-19 9:12 ` Laxman Dewangan [not found] ` <4F8FD709.60308-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> 2012-04-19 15:31 ` Stephen Warren 2012-04-19 15:31 ` Stephen Warren 2012-04-19 15:31 ` Stephen Warren 2012-04-24 7:42 ` Linus Walleij 2012-04-24 7:42 ` Linus Walleij 2012-04-24 7:42 ` Linus Walleij 2012-04-24 7:42 ` Linus Walleij 2012-04-24 21:08 ` Olof Johansson 2012-04-24 21:08 ` Olof Johansson 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=4F8D18A0.9030108@cam.ac.uk \ --to=jic23@cam.ac.uk \ --cc=bfreed@chromium.org \ --cc=broonie@opensource.wolfsonmicro.com \ --cc=cbouatmailru@gmail.com \ --cc=devel@driverdev.osuosl.org \ --cc=grant.likely@secretlab.ca \ --cc=gregkh@linuxfoundation.org \ --cc=grundler@chromium.org \ --cc=lars@metafoo.de \ --cc=ldewangan@nvidia.com \ --cc=linus.walleij@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-doc@vger.kernel.org \ --cc=linux-iio@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux@arm.linux.org.uk \ --cc=olof@lixom.net \ --cc=rdunlap@xenotime.net \ --cc=rob.herring@calxeda.com \ --cc=swarren@nvidia.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.