From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Linus Walleij <linusw@kernel.org>
Cc: jiale yao <19888972804@163.com>, Mark Brown <broonie@kernel.org>,
linux-spi@vger.kernel.org, Biju Das <biju.das.jz@bp.renesas.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: RE: Re:RE: [PATCH] pinctrl: mcp23s08: reject devices without match data
Date: Fri, 2 Oct 2026 13:18:54 +0300 [thread overview]
Message-ID: <ar-FDqxMC3F-zkPB@ashevche-desk.local> (raw)
In-Reply-To: <CAD++jL=eGjhCM8Xa=T08rPSGpH4p5dsajZa569gsObJma3yZ6g@mail.gmail.com>
On Fri, Oct 02, 2026 at 11:52:41AM +0200, Linus Walleij wrote:
> On Fri, Oct 2, 2026 at 8:59 AM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
>
> > I believe this is the whole design of driver_override like this...
> > There is an attempt to allow drivers to forbid that feature.
>
> I guess I don't have the right background to understand
> the driver_override feature, it feels someone should explain
> its virtues to me because I feel I am getting really angry
> at it and it may not deserve that.
>
> The entire name of the thing feels like debugfs-footgun
> territory for example.
Yeah, I can't find neither a thing on LWN.net nor in the in-tree documentation.
The only useful piece of information is (in kernel-doc of struct bus_type):
driver_override
Set to true if this bus supports the driver_override mechanism, which
allows userspace to force a specific driver to bind to a device via a sysfs
attribute.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-10-02 10:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 13:38 Jiale Yao
2026-09-26 10:07 ` Biju Das
2026-09-26 10:23 ` jiale yao
2026-09-26 10:28 ` jiale yao
2026-09-28 6:03 ` Biju Das
2026-09-28 7:24 ` jiale yao
2026-09-28 7:32 ` Biju Das
2026-09-28 7:54 ` jiale yao
2026-09-28 8:05 ` Biju Das
2026-10-01 20:07 ` Linus Walleij
2026-10-02 6:58 ` Andy Shevchenko
2026-10-02 9:52 ` Linus Walleij
2026-10-02 10:18 ` Andy Shevchenko [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=ar-FDqxMC3F-zkPB@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=19888972804@163.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=broonie@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@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®