From: phucduc.bui@gmail.com
To: wbg@kernel.org, andriy.shevchenko@intel.com,
David Lechner <david@lechnology.com>
Cc: andy@kernel.org, dlechner@baylibre.com,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
m32285159@gmail.com, nuno.sa@analog.com, phucduc.bui@gmail.com,
sozdayvek@gmail.com
Subject: [PATCH v4 0/2] counter: ti-eqep: Fix runtime PM leak and use devm_counter_add()
Date: Mon, 9 Nov 2026 15:43:40 +0700 [thread overview]
Message-ID: <20261109084342.51865-1-phucduc.bui@gmail.com> (raw)
From: bui duc phuc <phucduc.bui@gmail.com>
Hi,
This series picks up Stepan's v3 [1], which had no follow-up since
May, with William's agreement [2].
v4:
- Reword commit message of patch 1 as suggested by Andy
- Add patch 2 to use devm_counter_add() and drop ti_eqep_remove()
as suggested by William.
Link v3:
https://lore.kernel.org/all/20260529095834.2561-1-sozdayvek@gmail.com/
Link v2:
https://lore.kernel.org/all/20260525152137.7428-1-sozdayvek@gmail.com/
Link v1:
https://lore.kernel.org/all/20260523184448.7609-1-sozdayvek@gmail.com/
[1] https://lore.kernel.org/all/20260529095834.2561-1-sozdayvek@gmail.com/
[2] https://lore.kernel.org/all/20261106193208.4136410-1-wbg@kernel.org/
Compile-tested only.
Best regards,
Phuc
Stepan Ionichev (1):
counter: ti-eqep: Fix runtime PM leak on probe failure
bui duc phuc (1):
counter: ti-eqep: Use devm_counter_add()
drivers/counter/ti-eqep.c | 38 +++++++++++++++++++-------------------
1 file changed, 19 insertions(+), 19 deletions(-)
--
2.43.0
next reply other threads:[~2026-11-09 8:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 8:43 phucduc.bui [this message]
2026-11-09 8:43 ` [PATCH v4 1/2] counter: ti-eqep: Fix runtime PM leak on probe failure phucduc.bui
2026-11-09 23:23 ` Andy Shevchenko
2026-11-10 11:01 ` Bui Duc Phuc
2026-11-10 14:39 ` David Lechner
2026-11-09 8:43 ` [PATCH v4 2/2] counter: ti-eqep: Use devm_counter_add() phucduc.bui
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=20261109084342.51865-1-phucduc.bui@gmail.com \
--to=phucduc.bui@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=david@lechnology.com \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m32285159@gmail.com \
--cc=nuno.sa@analog.com \
--cc=sozdayvek@gmail.com \
--cc=wbg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.