From: patchwork-bot+linux-soc@kernel.org
To: Linus Walleij <linusw@kernel.org>
Cc: soc@kernel.org
Subject: Re: [GIT PULL] pinctrl qcom defconfg changes for v7.2
Date: Thu, 07 May 2026 13:12:14 +0000 [thread overview]
Message-ID: <177815953429.3933061.1558882552272426536.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <CAD++jLnf-3JivT-7MtCdnx9DRG2MMvvZWcsFdLxWM6416Nr=qg@mail.gmail.com>
Hello:
This pull request was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Wed, 6 May 2026 21:23:22 +0200 you wrote:
> Hi SoC mainatiners,
>
> this is a split-off of the defconfig changes affecting pincontrol
> for qcom platforms in the next kernel cycle.
>
> The changes from the pinctrl tree cause conflicts with the
> soc tree, at the same time it is nice to have these changes
> in the pinctrl tree for coherency.
>
> [...]
Here is the summary with links:
- [GIT,PULL] pinctrl qcom defconfg changes for v7.2
https://git.kernel.org/soc/soc/c/da501bcdb132
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-05-07 13:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 19:23 [GIT PULL] pinctrl qcom defconfg changes for v7.2 Linus Walleij
2026-05-07 13:12 ` patchwork-bot+linux-soc [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=177815953429.3933061.1558882552272426536.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=linusw@kernel.org \
--cc=soc@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