From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Linux pin control <linux-gpio@vger.kernel.org>
Cc: Linus Walleij <linusw@kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Andy Shevchenko <andy@kernel.org>
Subject: [GIT PULL] intel-pinctrl for 7.3-1
Date: Tue, 11 Aug 2026 16:50:40 +0200 [thread overview]
Message-ID: <ans2wKanSm6W5lSc@black.igk.intel.com> (raw)
Hi Linux pin control maintainers,
A small piece against Intel pin control drivers and associated. Was a long time
in Linux Next without any reported problems, please pull for v7.3-rc1.
Thanks,
With Best Regards,
Andy Shevchenko
The following changes since commit dc59e4fea9d83f03bad6bddf3fa2e52491777482:
Linux 7.2-rc1 (2026-06-28 12:01:31 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pinctrl/intel.git tags/intel-pinctrl-v7.3-1
for you to fetch changes up to 699fd26ba39c6659b9f5ebbdee9293b9b6936283:
pinctrl: intel: Remove redundant dev_err_probe() (2026-07-17 18:57:43 +0200)
----------------------------------------------------------------
intel-pinctrl for v7.3-1
* Enable CPLD pin control on UP Xtreme i12 board
* Miscellaneous cleanup
----------------------------------------------------------------
Andy Shevchenko (1):
Merge patch series "upboard pinctrl support for device id INTC1055"
Gary Wang (2):
pinctrl: tigerlake: add some pin groups and functions for INTC1055
pinctrl: upboard: add device id INTC1055 based UP boards support
Pan Chuang (1):
pinctrl: intel: Remove redundant dev_err_probe()
drivers/pinctrl/intel/pinctrl-intel.c | 2 +-
drivers/pinctrl/intel/pinctrl-tigerlake.c | 32 +++++++++++++++++++++++++++++++
drivers/pinctrl/pinctrl-upboard.c | 21 ++++++++++++++++++++
3 files changed, 54 insertions(+), 1 deletion(-)
--
With Best Regards,
Andy Shevchenko
next reply other threads:[~2026-08-11 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 14:50 Andy Shevchenko [this message]
2026-08-11 15:42 ` [GIT PULL] intel-pinctrl for 7.3-1 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=ans2wKanSm6W5lSc@black.igk.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=andy@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mika.westerberg@linux.intel.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.