From: Brian Masney <masneyb@onstation.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: surenderpolsani@gmail.com, knaack.h@gmx.de, lars@metafoo.de,
pmeerw@pmeerw.net, gregkh@linuxfoundation.org,
gregor.boirie@parrot.com, singhalsimran0@gmail.com,
maitysanchayan@gmail.com, eraretuya@gmail.com,
linux-iio@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, Jon Brenner <Jon.Brenner@ams.com>
Subject: Re: [PATCH v3] staging: iio: light: Replace symbolic permissions as per coding style
Date: Sat, 20 May 2017 14:36:35 -0400 [thread overview]
Message-ID: <20170520183635.GA4124@200591939db7> (raw)
In-Reply-To: <e374d59a-c216-a19b-a3a1-a26a862f0ae5@kernel.org>
On Sat, May 20, 2017 at 06:55:02PM +0100, Jonathan Cameron wrote:
> On 19/05/17 10:37, surenderpolsani@gmail.com wrote:
> >From: Surender Polsani <surenderpolsani@gmail.com>
> >
> >Fixed the following checkpatch.pl warnings:
> >octal permissions are more preferable than symbolic permissions
> >
> >Replaced DEVICE_ATTR family macros with DEVICE_ATTR_RW family
> >as suggested by Greg K-H. Changed attributes and function
> >names where ever required to satisfy internal macro definitions
> >like __ATTR__RW().
> >
> >Signed-off-by: Surender Polsani <surenderpolsani@gmail.com>
> Nicely presented patch, but it runs into the fact that some of these
> shouldn't exist as hand rolled attrs in the first place.
>
> Some of theses should be handled through the various info_mask and
> event_info_mask bitmaps + read_raw etc.
>
> This would be a much less mechanical change however...
>
> See inline and I'll try and pick out which ones.
>
> Brian is working on this driver as well at the moment so there may
> well be some clashes.
>
> Perhaps you two could confer on who will target what? Saves
> everyone time to work together!
You can apply this if you'd like. I just got 7 different hardware
samples from Jon this week that are supported by this driver. I haven't
gotten far yet with coding since I'm currently working on getting
them all setup so that it will be easy for me to test my upcoming
driver changes.
For my first patch series, I'm planning to migrate the driver to use
IIO channels, cleaning up the I2C calls, and runtime power management
support. Hopefully I'll have this to you for next weekend.
Brian
next prev parent reply other threads:[~2017-05-20 18:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 8:36 [PATCH] staging: iio: light: Replace symbolic permissions as per coding style surenderpolsani
2017-05-18 9:06 ` Greg KH
2017-05-19 7:03 ` [PATCH v2] " surenderpolsani
2017-05-19 7:15 ` Greg KH
2017-05-19 7:36 ` suri
2017-05-19 8:12 ` surenderpolsani
2017-05-19 8:20 ` Greg KH
2017-05-19 9:37 ` [PATCH v3] " surenderpolsani
2017-05-20 17:55 ` Jonathan Cameron
2017-05-20 18:36 ` Brian Masney [this message]
2017-05-21 10:55 ` 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=20170520183635.GA4124@200591939db7 \
--to=masneyb@onstation.org \
--cc=Jon.Brenner@ams.com \
--cc=devel@driverdev.osuosl.org \
--cc=eraretuya@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=gregor.boirie@parrot.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maitysanchayan@gmail.com \
--cc=pmeerw@pmeerw.net \
--cc=singhalsimran0@gmail.com \
--cc=surenderpolsani@gmail.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