From: Krzysztof Kozlowski <krzk@kernel.org> Date: 2020-09-21 21:03:21
Milo Kim's email in TI bounces with permanent error (550: Invalid
recipient). Last email from him on LKML was in 2017. Move Milo Kim to
credits and remove the separate driver entries for:
- TI LP855x backlight driver,
- TI LP8727 charger driver,
- TI LP8788 MFD (ADC, LEDs, charger and regulator) drivers.
Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
---
CREDITS | 3 +++
MAINTAINERS | 23 -----------------------
2 files changed, 3 insertions(+), 23 deletions(-)
From: Pavel Machek <hidden> Date: 2020-09-21 21:06:16
Hi!
Milo Kim's email in TI bounces with permanent error (550: Invalid
recipient). Last email from him on LKML was in 2017. Move Milo Kim to
credits and remove the separate driver entries for:
- TI LP855x backlight driver,
- TI LP8727 charger driver,
- TI LP8788 MFD (ADC, LEDs, charger and regulator) drivers.
Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
I believe normal way would be to mark the entries "orphaned", not to
drop them altogether. Plus, I believe someone from TI is likely to
step up.
Best regards,
Pavel
From: Krzysztof Kozlowski <krzk@kernel.org> Date: 2020-09-22 07:08:55
On Mon, 21 Sep 2020 at 23:06, Pavel Machek [off-list ref] wrote:
Hi!
quoted
Milo Kim's email in TI bounces with permanent error (550: Invalid
recipient). Last email from him on LKML was in 2017. Move Milo Kim to
credits and remove the separate driver entries for:
- TI LP855x backlight driver,
- TI LP8727 charger driver,
- TI LP8788 MFD (ADC, LEDs, charger and regulator) drivers.
Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
I believe normal way would be to mark the entries "orphaned", not to
drop them altogether. Plus, I believe someone from TI is likely to
step up.
These are entries for specific drivers so they are covered by the
subsystem maintainers. You believe someone will step up, I believe if
these were important for TI, they would find the person some time ago,
so the emails won't bounce... This was similar with BQ chargers where
Andrew's email was bouncing and after a few weeks it was fixed. To me
it looks like TI does not have any priority in maintaining separate
driver entries so what is the point to keep orphaned driver-entry? It
is not the case where we have an orphaned subsystem and we look for a
person to handle it...
Best regards,
Krzysztof
From: Mark Brown <broonie@kernel.org> Date: 2020-09-22 09:37:33
On Tue, Sep 22, 2020 at 09:08:37AM +0200, Krzysztof Kozlowski wrote:
On Mon, 21 Sep 2020 at 23:06, Pavel Machek [off-list ref] wrote:
quoted
I believe normal way would be to mark the entries "orphaned", not to
drop them altogether. Plus, I believe someone from TI is likely to
step up.
These are entries for specific drivers so they are covered by the
subsystem maintainers. You believe someone will step up, I believe if
these were important for TI, they would find the person some time ago,
so the emails won't bounce... This was similar with BQ chargers where
It's fairly common for mobile parts to get dropped relatively quickly as
the technology moves fairly quickly in that market, I think a lot of teh
parts that Milo was working on were mobile ones.
From: Dan Murphy <hidden> Date: 2020-09-22 11:37:05
All
On 9/22/20 4:36 AM, Mark Brown wrote:
On Tue, Sep 22, 2020 at 09:08:37AM +0200, Krzysztof Kozlowski wrote:
quoted
On Mon, 21 Sep 2020 at 23:06, Pavel Machek [off-list ref] wrote:
quoted
I believe normal way would be to mark the entries "orphaned", not to
drop them altogether. Plus, I believe someone from TI is likely to
step up.
These are entries for specific drivers so they are covered by the
subsystem maintainers. You believe someone will step up, I believe if
these were important for TI, they would find the person some time ago,
so the emails won't bounce... This was similar with BQ chargers where
It's fairly common for mobile parts to get dropped relatively quickly as
the technology moves fairly quickly in that market, I think a lot of teh
parts that Milo was working on were mobile ones.
These specific drivers don't see many patches applied to them. These
drivers did have a few patches this year to fix random bugs.
Since I have worked in these other subsystems if replacing the
Maintainer is desired over removal then my name and email can be added
like I did with Andrews.
Dan Murphy [off-list ref]
Dan
From: Krzysztof Kozlowski <krzk@kernel.org> Date: 2020-09-22 11:47:39
On Tue, 22 Sep 2020 at 13:36, Dan Murphy [off-list ref] wrote:
All
On 9/22/20 4:36 AM, Mark Brown wrote:
quoted
On Tue, Sep 22, 2020 at 09:08:37AM +0200, Krzysztof Kozlowski wrote:
quoted
On Mon, 21 Sep 2020 at 23:06, Pavel Machek [off-list ref] wrote:
quoted
I believe normal way would be to mark the entries "orphaned", not to
drop them altogether. Plus, I believe someone from TI is likely to
step up.
These are entries for specific drivers so they are covered by the
subsystem maintainers. You believe someone will step up, I believe if
these were important for TI, they would find the person some time ago,
so the emails won't bounce... This was similar with BQ chargers where
It's fairly common for mobile parts to get dropped relatively quickly as
the technology moves fairly quickly in that market, I think a lot of teh
parts that Milo was working on were mobile ones.
These specific drivers don't see many patches applied to them. These
drivers did have a few patches this year to fix random bugs.
Since I have worked in these other subsystems if replacing the
Maintainer is desired over removal then my name and email can be added
like I did with Andrews.
Dan Murphy [off-list ref]
I will add then yours name in v2 of this patch. Thanks for taking care of these.
Best regards,
Krzysztof