All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Breathitt Gray <wbg@kernel.org>
To: phucduc.bui@gmail.com
Cc: William Breathitt Gray <wbg@kernel.org>,
	andriy.shevchenko@intel.com, andy@kernel.org,
	dlechner@baylibre.com, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org, m32285159@gmail.com,
	nuno.sa@analog.com, sozdayvek@gmail.com
Subject: Re: [PATCH v3] counter: ti-eqep: use devm for runtime PM to
Date: Fri,  6 Nov 2026 14:32:07 -0500	[thread overview]
Message-ID: <20261106193208.4136410-1-wbg@kernel.org> (raw)
In-Reply-To: <20261102100031.5573-1-phucduc.bui@gmail.com>

On Mon, Nov 02, 2026 at 05:00:31PM +0700, phucduc.bui@gmail.com wrote:
> Hi Stepan,
> 
> William pointed me to this thread after I sent a similar patch. It
> looks like there has been no v4 since May. Are you still planning to
> send one? If not, I'm happy to pick it up, keeping you as the author,
> and address the comments from Andy and William.
> 
> Best regards,
> Phuc

Hi Phuc,

Go ahead and submit a v4 addressing the comments from Andy. Submit a
follow-up patch as well to eliminate the ti_eqep_remove() callback as
described in my earlier comment[^1] in this thread.

Thanks,

William Breathitt Gray

[^1]: https://lore.kernel.org/all/20260604021902.891327-1-wbg@kernel.org/

  reply	other threads:[~2026-11-06 19:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-29  9:58 [PATCH v3] counter: ti-eqep: use devm for runtime PM to fix probe error path Stepan Ionichev
2026-06-03  5:42 ` Andy Shevchenko
2026-08-02 12:59   ` William Breathitt Gray
2026-11-02 10:00     ` [PATCH v3] counter: ti-eqep: use devm for runtime PM to phucduc.bui
2026-11-06 19:32       ` William Breathitt Gray [this message]
2026-11-09  7:21         ` Bui Duc Phuc
2026-06-04  2:19 ` [PATCH v3] counter: ti-eqep: use devm for runtime PM to fix probe error path 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=20261106193208.4136410-1-wbg@kernel.org \
    --to=wbg@kernel.org \
    --cc=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --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=phucduc.bui@gmail.com \
    --cc=sozdayvek@gmail.com \
    /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.