Linux IIO development
 help / color / mirror / Atom feed
From: William Breathitt Gray <vilhelm.gray@gmail.com>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: linux-kernel@vger.kernel.org,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	David Jander <david@protonic.nl>,
	Robin van der Gracht <robin@protonic.nl>,
	linux-iio@vger.kernel.org, Jonathan Cameron <jic23@kernel.org>
Subject: Re: [PATCH v2 0/2] counter: push event on every pulse
Date: Fri, 11 Feb 2022 18:41:37 +0900	[thread overview]
Message-ID: <YgYvUdgkkWixDir4@shinobu> (raw)
In-Reply-To: <20220203135727.2374052-1-o.rempel@pengutronix.de>

[-- Attachment #1: Type: text/plain, Size: 678 bytes --]

On Thu, Feb 03, 2022 at 02:57:25PM +0100, Oleksij Rempel wrote:
> changes v2
> - rebase against latest kernel and fix some regressions
> - add COUNTER_EVENT_CHANGE_OF_STATE event
> 
> Add support of push even on every pulse.
> 
> Oleksij Rempel (2):
>   counter: add new COUNTER_EVENT_CHANGE_OF_STATE
>   counter: interrupt-cnt: add counter_push_event()
> 
>  drivers/counter/interrupt-cnt.c | 7 +++++--
>  include/uapi/linux/counter.h    | 2 ++
>  2 files changed, 7 insertions(+), 2 deletions(-)
> 
> -- 
> 2.30.2

Thank you Oleksij, I'm picking this up now and I'll submit it with the
rest of the Counter patches for this cycle.

William Breathitt Gray

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2022-02-11  9:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03 13:57 [PATCH v2 0/2] counter: push event on every pulse Oleksij Rempel
2022-02-03 13:57 ` [PATCH v2 1/2] counter: add new COUNTER_EVENT_CHANGE_OF_STATE Oleksij Rempel
2022-02-03 13:57 ` [PATCH v2 2/2] counter: interrupt-cnt: add counter_push_event() Oleksij Rempel
2022-02-04  7:35   ` William Breathitt Gray
2022-02-11  9:41 ` William Breathitt Gray [this message]

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=YgYvUdgkkWixDir4@shinobu \
    --to=vilhelm.gray@gmail.com \
    --cc=david@protonic.nl \
    --cc=jic23@kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    --cc=robin@protonic.nl \
    /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