From: Brian Masney <bmasney@redhat.com>
To: Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Joshua Henderson <joshua.henderson@microchip.com>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Brian Masney <bmasney@redhat.com>
Subject: [PATCH 0/3] pinctrl: pic32: allow driver to be compiled with COMPILE_TEST
Date: Sun, 22 Feb 2026 18:33:28 -0500 [thread overview]
Message-ID: <20260222-pinctrl-pic32-v1-0-db86248da18d@redhat.com> (raw)
While migrating a pic32 clk driver off of a legacy API, I mistakenly
broke one of the drivers, and the issue could have been caught with a
simple compile test. Now that the dependent patches have been merged
into Linus's tree via the MIPS tree, we can now enable COMPILE_TEST
for all of pic32 drivers in this subsystem.
While changes are being made to this driver, let's also fix any
outstanding checkpatch.pl errors with this driver.
Signed-off-by: Brian Masney <bmasney@redhat.com>
---
Brian Masney (3):
pinctrl: pic32: change all cases of bare 'unsigned' to 'unsigned int'
pinctrl: pic32: use consistent spacing around '+'
pinctrl: pic32: allow driver to be compiled with COMPILE_TEST
drivers/pinctrl/Kconfig | 2 +-
drivers/pinctrl/pinctrl-pic32.c | 42 ++++++++++++++++++++---------------------
2 files changed, 22 insertions(+), 22 deletions(-)
---
base-commit: 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f
change-id: 20260222-pinctrl-pic32-dcb7051a882b
Best regards,
--
Brian Masney <bmasney@redhat.com>
next reply other threads:[~2026-02-22 23:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-22 23:33 Brian Masney [this message]
2026-02-22 23:33 ` [PATCH 1/3] pinctrl: pic32: change all cases of bare 'unsigned' to 'unsigned int' Brian Masney
2026-02-22 23:33 ` [PATCH 2/3] pinctrl: pic32: use consistent spacing around '+' Brian Masney
2026-02-22 23:33 ` [PATCH 3/3] pinctrl: pic32: allow driver to be compiled with COMPILE_TEST Brian Masney
2026-02-23 9:50 ` [PATCH 0/3] " Bartosz Golaszewski
2026-02-24 9:25 ` Linus Walleij
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=20260222-pinctrl-pic32-v1-0-db86248da18d@redhat.com \
--to=bmasney@redhat.com \
--cc=brgl@kernel.org \
--cc=joshua.henderson@microchip.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®