From: "Danilo Krummrich" <dakr@kernel.org>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Saravana Kannan" <saravanak@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
<driver-core@lists.linux.dev>, <rust-for-linux@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Driver core changes for 7.0-rc1
Date: Mon, 02 Mar 2026 20:19:24 +0100 [thread overview]
Message-ID: <DGSJFB8RGH40.30AINI1WBAMMB@kernel.org> (raw)
In-Reply-To: <CAHk-=wjDwsXRcur+-Mf0UysmNP8Vz2XcETgdp60bJnK0Nm+C7Q@mail.gmail.com>
On Sun Mar 1, 2026 at 10:01 PM CET, Linus Torvalds wrote:
> So the thing that would matter is the longest actual real driver name.
> Aren't those typically just a few bytes (eg "regulator-bus-drv" or
> "__typec_altmode_driver" being long ones I find with a bad grep
> pattern that might miss millions of other cases)
Yes, generally they should be pretty short.
OOC, I asked an LLM to figure it out (so take this with the necessary grain of
salt):
Out of ~7,560 unique driver names:
┌────────────┬───────────┐
│ Threshold │ Count │
├────────────┼───────────┤
│ > 32 chars │ 6 (0.08%) │
├────────────┼───────────┤
│ > 48 chars │ 1 (0.01%) │
├────────────┼───────────┤
│ > 64 chars │ 0 │
└────────────┴───────────┘
Length distribution
1-10 chars: 3,513 (46.5%)
11-16 chars: 3,111 (41.1%)
17-24 chars: 880 (11.6%)
25-32 chars: 50 ( 0.7%)
33-49 chars: 6 ( 0.1%)
> IOW, it looks like it would be fine to just say "use just a 32-byte
> buffer" if a buffer is needed.
Assuming the above is roughly correct, you are pretty close. :)
> Of course, if no buffer is needed that's even better.
Yes, I don't think we ever need to obtain a copy other than through
sysfs_emit().
next prev parent reply other threads:[~2026-03-02 19:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 23:04 [GIT PULL] Driver core changes for 7.0-rc1 Danilo Krummrich
2026-02-12 3:58 ` pr-tracker-bot
2026-03-01 7:44 ` Linus Torvalds
2026-03-01 7:56 ` Linus Torvalds
2026-03-01 13:01 ` Gary Guo
2026-03-01 13:04 ` Danilo Krummrich
2026-03-01 18:17 ` Linus Torvalds
2026-03-01 20:21 ` Danilo Krummrich
2026-03-01 21:01 ` Linus Torvalds
2026-03-02 19:19 ` Danilo Krummrich [this message]
2026-03-01 18:20 ` Danilo Krummrich
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=DGSJFB8RGH40.30AINI1WBAMMB@kernel.org \
--to=dakr@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=saravanak@kernel.org \
--cc=torvalds@linux-foundation.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