Linux IIO development
 help / color / mirror / Atom feed
From: William Breathitt Gray <wbg@kernel.org>
To: gregkh@linuxfoundation.org, linux-iio@vger.kernel.org
Cc: William Breathitt Gray <wbg@kernel.org>
Subject: [GIT PULL] Counter updates for 7.2
Date: Tue,  2 Jun 2026 11:46:02 +0900	[thread overview]
Message-ID: <20260602024614.853294-1-wbg@kernel.org> (raw)

The following changes since commit 254f49634ee16a731174d2ae34bc50bd5f45e731:

  Linux 7.1-rc1 (2026-04-26 14:19:00 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/wbg/counter.git tags/counter-updates-for-7.2

for you to fetch changes up to ca815bb87064a8f68b00eaf8872ef0d4a33a5bf7:

  counter: intel-qep: Use devm_mutex_init() (2026-05-28 07:16:46 +0900)

----------------------------------------------------------------
Counter updates for 7.2

Manual mutex lock logic is replaced by lock guards in intel-qep.
Additionally, devm_mutex_init() is now used in ftm-quaddec,
interrupt-cnt, and intel-qep to handle mutex cleanup automatically.

----------------------------------------------------------------
Ilpo Järvinen (1):
      counter: intel-qep: Use devm_mutex_init()

Joao Paulo Menezes Linaris (1):
      counter: intel-qep: Replace manual mutex logic with lock guards

Stepan Ionichev (2):
      counter: ftm-quaddec: use devm_mutex_init()
      counter: interrupt-cnt: use devm_mutex_init()

 drivers/counter/ftm-quaddec.c   |  4 ++-
 drivers/counter/intel-qep.c     | 54 ++++++++++++++++-------------------------
 drivers/counter/interrupt-cnt.c |  4 ++-
 3 files changed, 27 insertions(+), 35 deletions(-)

             reply	other threads:[~2026-06-02  2:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-02  2:46 William Breathitt Gray [this message]
2026-06-08 19:26 ` [GIT PULL] Counter updates for 7.2 Greg KH

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=20260602024614.853294-1-wbg@kernel.org \
    --to=wbg@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox