From: Greg KH <gregkh@linuxfoundation.org>
To: Andi Shyti <andi@etezian.org>
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org, pc@asdf.org,
oatilla@gmail.com
Subject: Re: [PATCH 00/19] misc: bh1770glc features and fixes
Date: Mon, 17 Jun 2013 15:54:05 -0700 [thread overview]
Message-ID: <20130617225405.GC21613@kroah.com> (raw)
In-Reply-To: <cover.1371145891.git.andi@etezian.org>
On Thu, Jun 13, 2013 at 08:20:34PM +0200, Andi Shyti wrote:
> Hi,
>
> This patchset contains a collection of new features and fixes for
> the bh1770glc driver for the BH1770 and SFH7770 proximity
> and ambient light sensor device.
Remind me again why this isn't an drivers/iio/ driver, using that api?
> In few words this is what it brings:
> - /dev/input/event interface
> - removal obsolete and wrong parameters
What do you mean by this? Userspace parameters? Did you just change
the user/kernel api? Or something else?
> - new relevant parameters for glass attenuation and glass
> factor, lux compensation due to the LED cover or ink
Again, why not iio?
thanks,
greg k-h
next prev parent reply other threads:[~2013-06-17 22:54 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 18:20 [PATCH 00/19] misc: bh1770glc features and fixes Andi Shyti
2013-06-13 18:20 ` [PATCH 01/19] bh1770glc: added input device interface Andi Shyti
2013-06-17 22:52 ` Greg KH
2013-06-17 23:27 ` Andi Shyti
2013-06-17 23:36 ` Greg KH
2013-06-17 23:54 ` Andi Shyti
2013-06-17 23:55 ` Greg KH
2013-06-13 18:20 ` [PATCH 02/19] bh1770glc: different glass attenuation parameters Andi Shyti
2013-06-13 18:20 ` [PATCH 03/19] bh1770glc: lux0_glass_factor & lux0_comp_factor on sysfs Andi Shyti
2013-06-17 22:52 ` Greg KH
2013-06-17 23:28 ` Andi Shyti
2013-06-13 18:20 ` [PATCH 04/19] bh1770glc: Added raw lux output file for ALS to sysfs Andi Shyti
2013-06-13 18:20 ` [PATCH 05/19] bh1770glc: Removed obsolete offset settings from SFH7770 code Andi Shyti
2013-06-13 18:20 ` [PATCH 06/19] bh1770glc: removed proximity adjustement Andi Shyti
2013-06-13 18:20 ` [PATCH 07/19] bh1770glc: split read result function Andi Shyti
2013-06-13 18:20 ` [PATCH 08/19] bh1770glc: logic change in the proximity read Andi Shyti
2013-06-13 18:20 ` [PATCH 09/19] bh1770glc: use min_t instead of min Andi Shyti
2013-06-13 18:20 ` [PATCH 10/19] bh1770glc: use kstrtoul instead of strict_strtoul Andi Shyti
2013-06-13 18:20 ` [PATCH 11/19] bh1770glc: removed lux_read_raw_result() function Andi Shyti
2013-06-13 18:20 ` [PATCH 12/19] bh1770glc: Introduced dynamic threshold Andi Shyti
2013-06-13 18:20 ` [PATCH 13/19] bh1770glc: Code cleaning and aligning in source code Andi Shyti
2013-06-13 18:20 ` [PATCH 14/19] bh1770glc: Modified the neutral glass attenuation value Andi Shyti
2013-06-13 18:20 ` [PATCH 15/19] bh1770glc: Modified scaler variable Andi Shyti
2013-06-13 18:20 ` [PATCH 16/19] bh1770glc: Added sanity check for scf Andi Shyti
2013-06-13 18:20 ` [PATCH 17/19] bh1770glc: Implemented switch for interrupt operation Andi Shyti
2013-06-13 18:20 ` [PATCH 18/19] bh1770glc: Corrected proximity sensor rates Andi Shyti
2013-06-13 18:20 ` [PATCH 19/19] bh1770glc: Proximity sensor LED current update Andi Shyti
2013-06-17 22:54 ` Greg KH [this message]
2013-06-17 23:38 ` [PATCH 00/19] misc: bh1770glc features and fixes Andi Shyti
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=20130617225405.GC21613@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andi@etezian.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=oatilla@gmail.com \
--cc=pc@asdf.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