From: Stephen Warren <swarren@wwwdotorg.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: grant.likely@secretlab.ca, rob.herring@calxeda.com,
rob@landley.net, linux@arm.linux.org.uk, jic23@cam.ac.uk,
gregkh@linuxfoundation.org, swarren@nvidia.com, olof@lixom.net,
devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH V2 2/4] staging: iio: light: of: Fix vendor prefix of isl29018/isl29028
Date: Mon, 23 Apr 2012 11:17:19 -0600 [thread overview]
Message-ID: <4F958E9F.8070402@wwwdotorg.org> (raw)
In-Reply-To: <1335183097-21104-4-git-send-email-ldewangan@nvidia.com>
On 04/23/2012 06:11 AM, Laxman Dewangan wrote:
> ISL29018/ISL29028 is from Intersil Corporation and making the
> vendor prefix for this part as "isil" for OF compatibity.
>
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
I assume this patch will go through the staging tree. Let me know if you
want me to take it through the Tegra tree.
next prev parent reply other threads:[~2012-04-23 17:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 12:11 [PATCH V2 0/4] ARM: tegra: enable ALS and proximity sensors Laxman Dewangan
2012-04-23 12:11 ` [PATCH V2 1/4] devicetree: Document Intersil Corporation vendor prefix Laxman Dewangan
2012-04-23 17:16 ` Stephen Warren
2012-04-24 14:50 ` Rob Landley
2012-04-23 12:11 ` [PATCH V5] dmaengine: tegra: add dma driver Laxman Dewangan
2012-04-23 12:11 ` [PATCH V2 2/4] staging: iio: light: of: Fix vendor prefix of isl29018/isl29028 Laxman Dewangan
2012-04-23 17:17 ` Stephen Warren [this message]
2012-04-23 17:28 ` Greg KH
2012-04-23 17:43 ` Stephen Warren
2012-04-23 17:49 ` Greg KH
2012-04-24 6:13 ` Laxman Dewangan
2012-04-23 12:11 ` [PATCH V2 3/4] ARM: dt: tegra: enable als and proximity sensor Laxman Dewangan
2012-04-23 17:15 ` Stephen Warren
2012-04-26 17:39 ` Laxman Dewangan
2012-04-23 12:11 ` [PATCH V2 4/4] ARM: tegra: defconfig: add ISL29028 Laxman Dewangan
2012-04-23 17:16 ` Stephen Warren
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=4F958E9F.8070402@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@cam.ac.uk \
--cc=ldewangan@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=olof@lixom.net \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--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: 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