Linux IIO development
 help / color / mirror / Atom feed
From: William Breathitt Gray <william.gray@linaro.org>
To: gregkh@linuxfoundation.org
Cc: linux-iio@vger.kernel.org
Subject: [GIT PULL] First set of Counter fixes for 6.6
Date: Thu, 7 Sep 2023 18:32:55 -0400	[thread overview]
Message-ID: <ZPpPl8V97juxRNyT@ishi> (raw)

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

The following changes since commit 2dde18cd1d8fac735875f2e4987f11817cc0bc2c:

  Linux 6.5 (2023-08-27 14:49:51 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/wbg/counter.git tags/counter-fixes-for-6.6a

for you to fetch changes up to df8fdd01c98b99d04915c04f3a5ce73f55456b7c:

  counter: microchip-tcb-capture: Fix the use of internal GCLK logic (2023-09-05 12:25:14 -0400)

----------------------------------------------------------------
First set of Counter fixes for 6.6

The counter_get_ext() function would incorrectly refer to the first
element of the extensions array to handle component array extensions
when they are located at a different index; a fix is provided to index
to the correct element in the array for this case. A fix for the
microchip-tcb-capture is provided as well to correct an inverted
internal GCLK logic for clock selection.

----------------------------------------------------------------
Dharma Balasubiramani (1):
      counter: microchip-tcb-capture: Fix the use of internal GCLK logic

Fabrice Gasnier (1):
      counter: chrdev: fix getting array extensions

 drivers/counter/counter-chrdev.c        | 4 ++--
 drivers/counter/microchip-tcb-capture.c | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

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

             reply	other threads:[~2023-09-07 22:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-07 22:32 William Breathitt Gray [this message]
2023-10-02 11:14 ` [GIT PULL] First set of Counter fixes for 6.6 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=ZPpPl8V97juxRNyT@ishi \
    --to=william.gray@linaro.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