| Message ID | 20220808104712.54315-1-krzysztof.kozlowski@linaro.org |
|---|---|
| Headers | show |
| Series | iio/hwmon/mfd/leds/net/power/ASoC: dt-bindings: few stale maintainers cleanup | expand |
On 08/08/2022 13:47, Krzysztof Kozlowski wrote: > Emails to Dan Murphy bounce ("550 Invalid recipient <dmurphy@ti.com> > (#5.1.1)"). (...) > description: | > diff --git a/Documentation/devicetree/bindings/power/supply/bq25980.yaml b/Documentation/devicetree/bindings/power/supply/bq25980.yaml > index 4883527ab5c7..509a0667b04e 100644 > --- a/Documentation/devicetree/bindings/power/supply/bq25980.yaml > +++ b/Documentation/devicetree/bindings/power/supply/bq25980.yaml > @@ -8,7 +8,6 @@ $schema: http://devicetree.org/meta-schemas/core.yaml# > title: TI BQ25980 Flash Charger > > maintainers: > - - Dan Murphy <dmurphy@ti.com> > - Ricardo Rivera-Matos <r-rivera-matos@ti.com> Ricardo's also bounces... Does it mean TI is not interested in maintaining mainline support for its drivers? Best regards, Krzysztof
> Either way, I have several of these parts and can support these. Feel free > to replace Dan's email with my email if that works better. Please could you submit a patch to MAINTAINERS replacing Dan's name with your. I see lots of bounces from PHY driver patches because the get_maintainers script returns his address. Thanks Andrew
On 8/8/22 3:08 PM, Andrew Lunn wrote: >> Either way, I have several of these parts and can support these. Feel free >> to replace Dan's email with my email if that works better. > > Please could you submit a patch to MAINTAINERS replacing Dan's name > with your. I see lots of bounces from PHY driver patches because the > get_maintainers script returns his address. > I'm not seeing his name in the latest MAINTAINERS, seem they all got dropped in 57a9006240b2. Maybe the script returns his address based on commit signing. Not sure what the current solution to that would be, maybe .get_maintainer.ignore? Andrew > Thanks > Andrew
> I'm not seeing his name in the latest MAINTAINERS, seem they all got > dropped in 57a9006240b2. Ah, great. And there does not appear to be a MAINTAINERS entry for any of the TI PHYs, so giving the correct impression they are without a Maintainer. Andrew
On 08/08/2022 18:04, Andrew Davis wrote: > On 8/8/22 6:08 AM, Krzysztof Kozlowski wrote: >> On 08/08/2022 13:47, Krzysztof Kozlowski wrote: >>> Emails to Dan Murphy bounce ("550 Invalid recipient <dmurphy@ti.com> >>> (#5.1.1)"). >> >> >> (...) >> >>> description: | >>> diff --git a/Documentation/devicetree/bindings/power/supply/bq25980.yaml b/Documentation/devicetree/bindings/power/supply/bq25980.yaml >>> index 4883527ab5c7..509a0667b04e 100644 >>> --- a/Documentation/devicetree/bindings/power/supply/bq25980.yaml >>> +++ b/Documentation/devicetree/bindings/power/supply/bq25980.yaml >>> @@ -8,7 +8,6 @@ $schema: http://devicetree.org/meta-schemas/core.yaml# >>> title: TI BQ25980 Flash Charger >>> >>> maintainers: >>> - - Dan Murphy <dmurphy@ti.com> >>> - Ricardo Rivera-Matos <r-rivera-matos@ti.com> >> >> Ricardo's also bounces... Does it mean TI is not interested in >> maintaining mainline support for its drivers? >> > > TI is still interested in maintaining support here. But as we know folks > come and go, so giving specific emails might not be the best option. > Doesn't look like the schema here allows free-form strings, but if it did > I'd recommend the TI E2E Power-Management support forum[0] added. Any > questions on Linux/DT for these parts posted there would land on my desk > just the same, or to whomever is assigned in the future with maintaining > these drivers. Currently an email address is required. I am not sure if there is intention to change it, because similarly to MAINTAINERS file email is the way of our communication. Also in MAINTAINERS we expect to have person's address (with M:) and for the lists there is a separate entry. > Either way, I have several of these parts and can support these. Feel free > to replace Dan's email with my email if that works better. Yes, that would be great, thanks! Best regards, Krzysztof
On 08/08/2022 21:52, Jakub Kicinski wrote: > On Mon, 8 Aug 2022 13:47:07 +0300 Krzysztof Kozlowski wrote: >> Several of the bindings here had only one >> maintainer and history does not always point to a new one (although I did not >> perform extensive digging). I added subsystem maintainer, because dtschema >> requires such entry. This is not the best choice as simply subsystem maintainer >> might not have the actual device (or its datasheets or any interest in it). >> >> However dtschema requires a maintainer. Maybe we could add some >> "orphaned" entry in such case? > > Integrating it with MAINTAINERS would be another option worth exploring > although slightly tangential. > > How do you want this merged? It's all over the place subsystem-wise. I was thinking this could go via Rob's tree as fixes for current cycle, so your Ack would be great. If there is preference, I can split it per subsystem, but for such trivial updates it's a bit of a churn. Best regards, Krzysztof
On Tue, 9 Aug 2022 08:25:29 +0300 Krzysztof Kozlowski wrote: > On 08/08/2022 21:52, Jakub Kicinski wrote: > > Integrating it with MAINTAINERS would be another option worth exploring > > although slightly tangential. > > > > How do you want this merged? It's all over the place subsystem-wise. > > I was thinking this could go via Rob's tree as fixes for current cycle, > so your Ack would be great Sounds good!