From: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
To: Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Andy Shevchenko <andriy.shevchenko@intel.com>,
Yu-Chun Lin <eleanor.lin@realtek.com>
Cc: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
James Tai <james.tai@realtek.com>,
Tzuyi Chang <tychang@realtek.com>,
CY Huang <cy.huang@realtek.com>,
Stanley Chang <stanley_chang@realtek.com>
Subject: Re: [PATCH v3 0/7] gpio: rtd1625: minor cleanups and log improvements
Date: Wed, 26 Aug 2026 17:08:10 +0200 [thread overview]
Message-ID: <178775688405.67048.8153038759125205303.b4-ty@oss.qualcomm.com> (raw)
In-Reply-To: <20260816-gpio-cleanup-v3-0-f298cdd65fca@realtek.com>
On Sun, 16 Aug 2026 23:17:29 +0800, Yu-Chun Lin wrote:
> This series splits the previous cleanup patch into smaller, logical
> pieces and addresses the review comments from Andy Shevchenko.
>
> Link: https://lore.kernel.org/lkml/anUcSPcJjJkLh0Z-@ashevche-desk.local/
>
>
Applied, thanks!
[1/7] gpio: rtd1625: Remove unnecessary blank line
https://git.kernel.org/brgl/c/f60178ca784aeeac3552383253e463d7e9d91620
[2/7] gpio: rtd1625: Drop unneeded initializations
https://git.kernel.org/brgl/c/097d950bb33edb708f3ea40453ade989cbd8c283
[3/7] gpio: rtd1625: Fix variable type for regmap_read()
https://git.kernel.org/brgl/c/d54bcfc3402fff60f38028a3ddf4e21cb0700fe2
[4/7] gpio: rtd1625: Narrow 'i' variable scope in loop
https://git.kernel.org/brgl/c/f5440a157b062e0bc67196614b6a24649533d495
[5/7] gpio: rtd1625: Narrow 'hwirq' variable scope in loop
https://git.kernel.org/brgl/c/7e9d11c9abf5e856208c0a3f3f32671f2861f4a8
[6/7] gpio: rtd1625: Replace pr_err_ratelimited() with dev_err_ratelimited()
https://git.kernel.org/brgl/c/a3902d376dd2e384931aa10c077005547b9c2ba8
[7/7] gpio: rtd1625: Use IRQ_TYPE_DEFAULT macro
https://git.kernel.org/brgl/c/d42c1df90df49b19c063d029c7d67e91751edc96
Best regards,
--
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
prev parent reply other threads:[~2026-08-26 15:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-16 15:17 [PATCH v3 0/7] gpio: rtd1625: minor cleanups and log improvements Yu-Chun Lin
2026-08-16 15:17 ` [PATCH v3 1/7] gpio: rtd1625: Remove unnecessary blank line Yu-Chun Lin
2026-08-17 8:13 ` Andy Shevchenko
2026-08-16 15:17 ` [PATCH v3 2/7] gpio: rtd1625: Drop unneeded initializations Yu-Chun Lin
2026-08-17 8:14 ` Andy Shevchenko
2026-08-16 15:17 ` [PATCH v3 3/7] gpio: rtd1625: Fix variable type for regmap_read() Yu-Chun Lin
2026-08-16 15:17 ` [PATCH v3 4/7] gpio: rtd1625: Narrow 'i' variable scope in loop Yu-Chun Lin
2026-08-17 8:14 ` Andy Shevchenko
2026-08-16 15:17 ` [PATCH v3 5/7] gpio: rtd1625: Narrow 'hwirq' " Yu-Chun Lin
2026-08-17 8:15 ` Andy Shevchenko
2026-08-16 15:17 ` [PATCH v3 6/7] gpio: rtd1625: Replace pr_err_ratelimited() with dev_err_ratelimited() Yu-Chun Lin
2026-08-16 15:17 ` [PATCH v3 7/7] gpio: rtd1625: Use IRQ_TYPE_DEFAULT macro Yu-Chun Lin
2026-08-26 15:08 ` Bartosz Golaszewski [this message]
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=178775688405.67048.8153038759125205303.b4-ty@oss.qualcomm.com \
--to=bartosz.golaszewski@oss.qualcomm.com \
--cc=andriy.shevchenko@intel.com \
--cc=brgl@kernel.org \
--cc=cy.huang@realtek.com \
--cc=eleanor.lin@realtek.com \
--cc=james.tai@realtek.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stanley_chang@realtek.com \
--cc=tychang@realtek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox