From: William Breathitt Gray <vilhelm.gray@gmail.com>
To: Patrick Havelange <patrick.havelange@essensium.com>,
Jonathan Cameron <jic23@kernel.org>,
gregkh@linuxfoundation.org
Cc: linux-iio@vger.kernel.org, fabrice.gasnier@st.com,
benjamin.gaignard@st.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
akpm@linux-foundation.org
Subject: Re: New IIO/counter driver
Date: Tue, 8 Jan 2019 09:46:32 +0900 [thread overview]
Message-ID: <20190108004632.GA3247@icarus> (raw)
In-Reply-To: <CAKKE0ZHmODzhvjPNJFVgT2cF_F=f2kNKr5K_CGP+0XgA5XZokw@mail.gmail.com>
On Mon, Jan 07, 2019 at 02:45:37PM +0100, Patrick Havelange wrote:
> Hello,
>
> I'm in the process of adding a new IIO/counter driver, however I also saw
> that there was a work in progress to have a separate counter subsystem (
> https://marc.info/?l=linux-iio&m=153974167727206 ). But it seems there is
> no recent progress on it.
> What is the state of those patches ? Is it still interesting to develop the
> driver as an IIO/counter , or should I use already that new subsystem ?
>
> Best Regards,
>
> Patrick Havelange.
Hello,
I am still open to merging this patchset and maintaining the Counter
subsystem. However, I took the lack of response for my latest
submission to indicate a loss of interest in this patchset's approach.
If there are still people who want this, I can rebase and resend this
patchset for submission; the past few versions have primarily been code
clarity and documentation changes so I believe the core design itself is
somewhat stable now.
Just let me know how best to proceed and I shall be happy to oblige --
whether to continue maintaining this patchset or to drop this design in
favor of improving the existing IIO Counter code in the kernel.
I'll CC those from the patchset submission to keep them in the loop.
Sincerely,
William Breathitt Gray
next parent reply other threads:[~2019-01-08 0:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKKE0ZHmODzhvjPNJFVgT2cF_F=f2kNKr5K_CGP+0XgA5XZokw@mail.gmail.com>
2019-01-08 0:46 ` William Breathitt Gray [this message]
2019-01-08 10:57 ` New IIO/counter driver Benjamin Gaignard
2019-01-08 11:01 ` Fabrice Gasnier
2019-01-12 17: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=20190108004632.GA3247@icarus \
--to=vilhelm.gray@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=benjamin.gaignard@st.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrice.gasnier@st.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick.havelange@essensium.com \
--cc=pmeerw@pmeerw.net \
/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).