Linux IIO development
 help / color / mirror / Atom feed
From: William Breathitt Gray <vilhelm.gray@gmail.com>
To: gregkh@linuxfoundation.org
Cc: jic23@kernel.org, linux-iio@vger.kernel.org,
	William Breathitt Gray <vilhelm.gray@gmail.com>
Subject: [PATCH 0/3] Counter subsystem changes for the 5.17 cycle
Date: Tue, 21 Dec 2021 17:16:45 +0900	[thread overview]
Message-ID: <cover.1640072890.git.vilhelm.gray@gmail.com> (raw)

There are only a few changes for the 5.17 cycle: a fix for missing
colons in the comments of struct counter_comp, a minor improvement in
the access of private data in the ti-eqep driver, and bug fix for the
interrupt enablement code of the 104-quad-8 driver. Due to the small
number of patches, the respective changes are submitted here as a patch
series.

Uwe Kleine-König (1):
  counter: ti-eqep: Use container_of instead of struct
    counter_device::priv

William Breathitt Gray (1):
  counter: 104-quad-8: Fix persistent enabled events bug

Yanteng Si (1):
  counter: Add the necessary colons and indents to the comments of
    counter_compi

 drivers/counter/104-quad-8.c | 82 +++++++++++++++++-------------------
 drivers/counter/ti-eqep.c    | 23 ++++++----
 include/linux/counter.h      | 40 +++++++++---------
 3 files changed, 73 insertions(+), 72 deletions(-)


base-commit: 1b18af40c1db195619e611faaeae624d6319b1f1
-- 
2.33.1


             reply	other threads:[~2021-12-21  8:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-21  8:16 William Breathitt Gray [this message]
2021-12-21  8:16 ` [PATCH 1/3] counter: Add the necessary colons and indents to the comments of counter_compi William Breathitt Gray
2021-12-21  8:16 ` [PATCH 2/3] counter: ti-eqep: Use container_of instead of struct counter_device::priv William Breathitt Gray
2021-12-21  8:16 ` [PATCH 3/3] counter: 104-quad-8: Fix persistent enabled events bug William Breathitt Gray

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=cover.1640072890.git.vilhelm.gray@gmail.com \
    --to=vilhelm.gray@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jic23@kernel.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