From: Harvey <harv@gmx.de>
To: "Michał Kępień" <kernel@kempniu.pl>,
"Jonathan Woithe" <jwoithe@just42.net>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>,
Platform Driver <platform-driver-x86@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] platform/x86: fujitsu-laptop: Fix radio LED detection
Date: Tue, 31 Oct 2017 11:54:05 +0100 [thread overview]
Message-ID: <683ac1cb-abf5-8d16-d016-8cbb4a75964e@gmx.de> (raw)
In-Reply-To: <20171031042002.GA9788@larwa.localdomain>
[-- Attachment #1.1: Type: text/plain, Size: 1200 bytes --]
> I agree as well. The erroneous log messages will only be generated when
> any rfkill device in the system is enabled or disabled, so IMHO this is
> mostly a nuisance thus can be handled when convenient.
FWIW: They are generated several times during every startup of the machine:
sudo journalctl -b | grep radio_led
718:Okt 31 11:46:21 gruenix kernel: leds fujitsu::radio_led: Setting an
LED's brightness failed (-2147483648)
744:Okt 31 11:46:22 gruenix kernel: leds fujitsu::radio_led: Setting an
LED's brightness failed (-2147483648)
760:Okt 31 11:46:22 gruenix kernel: leds fujitsu::radio_led: Setting an
LED's brightness failed (-2147483648)
790:Okt 31 11:46:22 gruenix kernel: leds fujitsu::radio_led: Setting an
LED's brightness failed (-2147483648)
793:Okt 31 11:46:22 gruenix kernel: leds fujitsu::radio_led: Setting an
LED's brightness failed (-2147483648)
893:Okt 31 11:46:29 gruenix kernel: leds fujitsu::radio_led: Setting an
LED's brightness failed (-2147483648)
But, yes. This is only a cosmetic issue. There don't seem to be too many
people reportig this as well.
Greetings
Harvey
--
I am root. If you see me laughing, you'd better have a backup!
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2017-10-31 10:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 4:29 Michał Kępień
2017-10-25 6:33 ` Jonathan Woithe
2017-10-25 13:11 ` Harvey
2017-10-27 16:49 ` Andy Shevchenko
2017-10-29 21:28 ` Michał Kępień
2017-10-30 11:21 ` Andy Shevchenko
2017-10-30 12:12 ` Jonathan Woithe
2017-10-30 14:13 ` Andy Shevchenko
2017-10-31 4:20 ` Michał Kępień
2017-10-31 10:54 ` Harvey [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=683ac1cb-abf5-8d16-d016-8cbb4a75964e@gmx.de \
--to=harv@gmx.de \
--cc=andy.shevchenko@gmail.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=jwoithe@just42.net \
--cc=kernel@kempniu.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@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®