From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: Pavel Machek <pavel@ucw.cz>,
"Enrico Weigelt, metux IT consult" <info@metux.net>
Cc: linux-kernel@vger.kernel.org, jacek.anaszewski@gmail.com,
dmurphy@ti.com, linux-leds@vger.kernel.org
Subject: Re: [PATCH 1/6] leds: apu: drop superseeded apu2/3 led support
Date: Wed, 17 Jul 2019 16:28:27 +0200 [thread overview]
Message-ID: <da2dccb7-f2f5-42b5-2549-ba67ecd568cb@metux.net> (raw)
In-Reply-To: <20190716193001.GG10400@amd>
On 16.07.19 21:30, Pavel Machek wrote:
Hi,
> Ok, so I understand the reasons, but people updating from old kernels
> (make oldconfig) will see nothing and their LEDs will stop working.
>
> Can we do something to help them?
I could announce that in pcengines forum. There've been several
discussions on this matter, replying there should give the participants
an automatic mail.
So far, I haven't seen any distro that enabled the old driver, so I
guess the actual users all compiled the kernel on their own and should
notice the change early enough.
--mtx
--
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287
next prev parent reply other threads:[~2019-07-17 14:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 14:57 leds: apu: drop obsolete support for apu>=2 Enrico Weigelt, metux IT consult
2019-07-15 14:57 ` [PATCH 1/6] leds: apu: drop superseeded apu2/3 led support Enrico Weigelt, metux IT consult
2019-07-16 19:30 ` Pavel Machek
2019-07-17 14:28 ` Enrico Weigelt, metux IT consult [this message]
2019-07-15 14:57 ` [PATCH 2/6] leds: apu: drop enum_apu_led_platform_types Enrico Weigelt, metux IT consult
2019-07-16 19:25 ` Pavel Machek
2019-07-15 14:57 ` [PATCH 3/6] leds: apu: drop iosize field from priv data Enrico Weigelt, metux IT consult
2019-07-16 19:25 ` Pavel Machek
2019-07-15 14:57 ` [PATCH 4/6] leds: apu: drop profile " Enrico Weigelt, metux IT consult
2019-07-16 19:26 ` Pavel Machek
2019-07-15 14:57 ` [PATCH 5/6] leds: apu: fix error on probing failure Enrico Weigelt, metux IT consult
2019-07-16 19:28 ` Pavel Machek
2019-07-17 14:29 ` Enrico Weigelt, metux IT consult
2019-07-17 16:37 ` Jacek Anaszewski
2019-07-22 12:08 ` [PATCH v2] leds: apu: fix error message " Enrico Weigelt, metux IT consult
2019-07-22 12:26 ` Pavel Machek
2019-07-15 14:57 ` [PATCH 6/6] leds: apu: add pr_fmt prefix for better log output Enrico Weigelt, metux IT consult
2019-07-16 19:28 ` Pavel Machek
2019-07-22 20:12 ` leds: apu: drop obsolete support for apu>=2 Jacek Anaszewski
2019-08-29 9:08 ` Enrico Weigelt, metux IT consult
2019-08-29 19:51 ` Jacek Anaszewski
2019-09-24 12:42 ` Enrico Weigelt, metux IT consult
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=da2dccb7-f2f5-42b5-2549-ba67ecd568cb@metux.net \
--to=lkml@metux.net \
--cc=dmurphy@ti.com \
--cc=info@metux.net \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
/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;
as well as URLs for NNTP newsgroup(s).