[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180106141752.7d4e5c93@archlinux>
Date: Sat, 6 Jan 2018 14:17:52 +0000
From: Jonathan Cameron <jic23@...nel.org>
To: Julia Lawall <julia.lawall@...6.fr>
Cc: Lars-Peter Clausen <lars@...afoo.de>,
Aishwarya Pant <aishpant@...il.com>,
Hartmut Knaack <knaack.h@....de>,
Peter Meerwald-Stadler <pmeerw@...erw.net>,
linux-iio@...r.kernel.org, linux-kernel@...r.kernel.org,
Joe Perches <joe@...ches.com>
Subject: Re: [PATCH 1/5] iio: buffer: use permission specific variants of
DEVICE_ATTR
On Sat, 6 Jan 2018 14:18:58 +0100 (CET)
Julia Lawall <julia.lawall@...6.fr> wrote:
> On Sat, 6 Jan 2018, Lars-Peter Clausen wrote:
>
> > On 01/06/2018 01:35 PM, Jonathan Cameron wrote:
> > > On Thu, 4 Jan 2018 20:07:14 +0530
> > > Aishwarya Pant <aishpant@...il.com> wrote:
> > >
> > >> This is a clean-up patch which replaces DEVICE_ATTR macro with the file
> > >> permission specific DEVICE_ATTR_{RO/WO/RW} macros for compaction and
> > >> readability. Done using coccinelle.
> > >
> > > Hmm. I'll be honest, I personally really dislike these macros.
> > > They absolutely don't help with readability because they obscure
> > > the connection between the attributes being created and their callbacks.
> > > Short is not the same as more readable.
> >
> > FWIW fully agreed.
>
> Could there be variants that keep the function names as arguments, but
> keep the benefit of the simpler permission specification and ensuring that
> the right functions are provided for the given permissions?
Yes, that would bring the benefits without the readability cost.
No one needs to know that RW means some octal number after all.
Jonathan
>
> julia
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists