[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210610141057.00007361@Huawei.com>
Date: Thu, 10 Jun 2021 14:10:57 +0100
From: Jonathan Cameron <Jonathan.Cameron@...wei.com>
To: Paul Cercueil <paul@...pouillou.net>
CC: Andy Shevchenko <andy.shevchenko@...il.com>,
Jonathan Cameron <jic23@...nel.org>,
Lars-Peter Clausen <lars@...afoo.de>,
Michael Hennerich <michael.hennerich@...log.com>,
linux-iio <linux-iio@...r.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] iio: core: Support removing extended name in
attribute filename
On Thu, 10 Jun 2021 14:05:53 +0100
Paul Cercueil <paul@...pouillou.net> wrote:
> Hi Andy,
>
> Le jeu., juin 10 2021 at 15:58:51 +0300, Andy Shevchenko
> <andy.shevchenko@...il.com> a écrit :
> > On Thu, Jun 10, 2021 at 3:47 PM Paul Cercueil <paul@...pouillou.net>
> > wrote:
> >>
> >> By default, when a channel has an extended name, it will appear in
> >> the
> >> filename of channel attributes. E.g. if the extended name is "aux",
> >> the
> >> filename of a "sample_rate" attribute will be something like:
> >> in_voltage0_aux_sample_rate
> >>
> >> Add a mechanism to disable this feature. This will be used to add a
> >> "extended_name" channel attribute.
> >
> > I'm afraid, NAK. Otherwise, please put an explanation that clearly
> > shows that it will be no ABI breakage.
> > I.o.w. users for the existing drivers and devices will always get
> > those attributes at the same platform configuration(s).
>
> Well, the commit message says that I'm adding a mechanism to disable
> the feature. If it was actually doing anything else (like actually
> disabling it for any attribute) then I'd mention it in the commit
> message.
>
> I don't see how that possibly can be a ABI breakage.
Ah. Both Andy and I got taken in by 'removing' in the title.
What you really mean is identifying the extended name. That's
much more acceptable :)
Jonathan
>
> -Paul
>
>
Powered by blists - more mailing lists