From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Petter Reinholdtsen <pere@debian.org>
Cc: lewart3@gmail.com,
Alexander Usyskin <alexander.usyskin@intel.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org
Subject: Re: mei modalias files missing device name and newline
Date: Tue, 21 Jan 2025 09:22:56 +0100 [thread overview]
Message-ID: <2025012120-dusk-remnant-da88@gregkh> (raw)
In-Reply-To: <sa6wmeoy3vy.fsf@hjemme.reinholdtsen.name>
On Tue, Jan 21, 2025 at 09:20:33AM +0100, Petter Reinholdtsen wrote:
> [Greg Kroah-Hartman]
> > There's no "requirement" that modalias sysfs files have to have a
> > trailing newline, so why is this considered "missing"?
>
> This all started when it was discovered that after more than 8 years,
> this one liner no longer worked as well as it used to:
>
> cat $(find /sys/devices -name modalias) | sort -u
>
> > Not all, most. If you want them all to, then we must sweep the whole
> > tree and fix them up. And then deal with any fallout where that
> > happens to break things :)
>
> >From my perspective, as the author of the isenkram package, it was the
> introduction of entries without newlines that broke things, not the
> other way around.
So this file has always not had a newline on the end?
Anyway, I'm not objecting to the change, but it needs to be submitted in
a format we can apply it in, AND all other modalias files need to be
fixed up as well to provide a \n on the end. The first one I found
turned out not to have that, so out of a "random sample" that was either
a lucky guess, or a sign that there is no consistancy here at all.
thanks,
greg k-h
next prev parent reply other threads:[~2025-01-21 8:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 23:30 Daniel Lewart
2025-01-21 8:04 ` Greg Kroah-Hartman
2025-01-21 8:20 ` Petter Reinholdtsen
2025-01-21 8:22 ` Greg Kroah-Hartman [this message]
2025-01-21 9:02 ` Petter Reinholdtsen
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=2025012120-dusk-remnant-da88@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alexander.usyskin@intel.com \
--cc=arnd@arndb.de \
--cc=lewart3@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pere@debian.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®