From: Mark Brown <broonie@kernel.org>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Linus Walleij <linusw@kernel.org>, Frank Li <Frank.Li@nxp.com>,
Josua Mayer <josua@solid-run.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Ulf Hansson <ulfh@kernel.org>
Subject: Re: linux-next: manual merge of the pinctrl tree with the mmc tree
Date: Fri, 10 Apr 2026 14:42:57 +0100 [thread overview]
Message-ID: <adj-YUqjWqfbr8Li@sirena.co.uk> (raw)
In-Reply-To: <CAPDyKFq_0+5gu3OEuvXSxnkVVxY4wKd6iHTFHMHJrXJaRkjfmQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 824 bytes --]
On Fri, Apr 10, 2026 at 03:36:48PM +0200, Ulf Hansson wrote:
> On Fri, 10 Apr 2026 at 15:31, Mark Brown <broonie@kernel.org> wrote:
> > > Indeed since making it I see more failures due to devm_mux_control_get()
> > > not being exported, I have a hard time seeing how exactly
> > > devm_get_mux_control_from_np() is intended to work given that it ignores
> > > the np parameter and is just a straight rename/reprototype of that
> > > function.
> Linus, if possible, I suggest you drop the patch from your pinctrl tree.
> If it's urgent to get this into v7.1 for pinctrl, you may pull my
> immutable mux branch from my mmc tree and let the author of the patch
> base the mux change on that.
It turns out there's also a build failure resulting from another commit
in that series so I really think it needs a bit more time.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-04-10 13:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 13:27 linux-next: manual merge of the pinctrl tree with the mmc tree Mark Brown
2026-04-10 13:31 ` Mark Brown
2026-04-10 13:36 ` Ulf Hansson
2026-04-10 13:42 ` Mark Brown [this message]
2026-04-10 18:10 ` Linus Walleij
-- strict thread matches above, loose matches on Subject: below --
2023-02-16 1:40 Stephen Rothwell
2023-02-23 0:13 ` Stephen Rothwell
2023-02-23 9:58 ` Emil Renner Berthing
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=adj-YUqjWqfbr8Li@sirena.co.uk \
--to=broonie@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=josua@solid-run.com \
--cc=linusw@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=ulfh@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