From: Jonathan Cameron <jic23@kernel.org>
To: Denis CIOCCA <denis.ciocca@st.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [PATCH 05/11] iio:st sensors: remove custom sampling frequence attribute in favour of core support.
Date: Sun, 24 Nov 2013 20:58:55 +0000 [thread overview]
Message-ID: <5292688F.9050501@kernel.org> (raw)
In-Reply-To: <ca9fd1ad-43a0-45a7-ab11-fde361636797@email.android.com>
On 11/21/13 15:03, Jonathan Cameron wrote:
>
>
> Denis CIOCCA <denis.ciocca@st.com> wrote:
>> Hi Jonathan,
>>
>> I think is a good thing do the porting some features inside the
>> framework, but I think is also important don't change the userspace
>> interface.
>>
>> For example now we are developing same libraries and applications that
>> using those files. What do you think to add on each driver one sysfs
>> file called 'version' that will be updated when the userspace interface
>>
>> is changed?
> Unfortunately the chances are that an app won't read it so that doesn't get around abi changes.
btw, the intent with this series is not to change the userspace interface. If I have
then it is a bug so please do point it out!
>
>>
>> Thanks,
>> Denis
>
next prev parent reply other threads:[~2013-11-24 20:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 12:28 [PATCH 05/11] iio:st sensors: remove custom sampling frequence attribute in favour of core support Denis CIOCCA
2013-11-21 15:03 ` Jonathan Cameron
2013-11-24 20:58 ` Jonathan Cameron [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-11-17 15:14 [RFC PATCH 00/11] IIO: Add core support for _available interfaces Jonathan Cameron
2013-11-17 15:14 ` [PATCH 05/11] iio:st sensors: remove custom sampling frequence attribute in favour of core support Jonathan Cameron
2013-11-18 18:25 ` Lars-Peter Clausen
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=5292688F.9050501@kernel.org \
--to=jic23@kernel.org \
--cc=denis.ciocca@st.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.