From: Jonathan Cameron <jic23@kernel.org>
To: Brian Masney <masneyb@onstation.org>
Cc: gregkh@linuxfoundation.org, linux-iio@vger.kernel.org,
devel@driverdev.osuosl.org
Subject: Re: [PATCH 4/4] staging: iio: isl29018: move out of staging
Date: Sun, 9 Oct 2016 11:39:44 +0100 [thread overview]
Message-ID: <1cde5244-0882-a1dc-a12d-84d9f5b4bd6d@kernel.org> (raw)
In-Reply-To: <20161009103511.GA26215@basecamp.onstation.org>
On 09/10/16 11:35, Brian Masney wrote:
> On Sun, Oct 09, 2016 at 10:45:12AM +0100, Jonathan Cameron wrote:
>> On 07/10/16 01:48, Brian Masney wrote:
>>> Move ISL29018/ISL29023/ISL29035 driver out of staging into mainline.
>>>
>>> Signed-off-by: Brian Masney <masneyb@onstation.org>
>> Time for a nitpick tastic review ;)
>>
>> The nature of a move out of staging patch is that we'll go over it
>> with the level of fine toothed comb we apply to a new submission.
>> A good part of my aim here is to ensure that once it's out it doesn't
>> get a lot of churn from whitespace or comment syntax patches etc.
>>
>> I want to be able to ignore it for ever more and have it continue to
>> work perfectly and be beautiful code ;)
>>
>> Anyhow, nothing of any significance at all in here, but it will need
>> a couple of precursor patches to clean up the loose ends before we
>> move it out of staging.
>>
>> Thanks for doing this and sorry to bounce it back to you over such
>> trivial stuff!
>
> Thanks, Jonathan, for taking the time to go through this. I'll send a
> second patch series in a day or two.
>
> I'm hoping to have one of these light sensors (along with 2 others in
> staging/iio/light/) in a week or so that I can hook it up to a
> Raspberry Pi to test the drivers. I ordered the sensors off of
> Digi-Key for a few dollars each. One of my friends is mounting them
> onto a breakout board for me.
>
> Is my change that renames the Kconfig variable acceptable? After I
> emailed that last patch set, I noticed that the description in Kconfig
> for this driver has 'ISL 29018' but the neighboring one in mainline has
> 'Intersil ISL29125' so I assume that should be changed as well for
> consistency.
Just realised I didn't press send on my reply to that one.
Upshot is unfortunately no. Feel free to fix the description though!
Jonathan
>
> Brian
>
next prev parent reply other threads:[~2016-10-09 10:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 0:48 [PATCH 1/4] staging: iio: isl29018: add documentation about the infrared suppression Brian Masney
2016-10-07 0:48 ` [PATCH 2/4] staging: iio: isl29018: document device tree bindings Brian Masney
2016-10-09 8:48 ` Jonathan Cameron
2016-10-07 0:48 ` [PATCH 3/4] staging: iio: isl29018: rename Kconfig variable to match existing light drivers in mainline Brian Masney
2016-10-09 10:33 ` Jonathan Cameron
2016-10-07 0:48 ` [PATCH 4/4] staging: iio: isl29018: move out of staging Brian Masney
2016-10-09 9:45 ` Jonathan Cameron
2016-10-09 10:35 ` Brian Masney
2016-10-09 10:39 ` Jonathan Cameron [this message]
2016-10-09 8:43 ` [PATCH 1/4] staging: iio: isl29018: add documentation about the infrared suppression Jonathan Cameron
2016-10-09 8:51 ` Jonathan Cameron
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=1cde5244-0882-a1dc-a12d-84d9f5b4bd6d@kernel.org \
--to=jic23@kernel.org \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-iio@vger.kernel.org \
--cc=masneyb@onstation.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).