Should get_maintainer.pl ignore obsolete Qualcomm domains?

Should get_maintainer.pl ignore obsolete Qualcomm domains?

[Jeff Johnson]

Qualcomm employees have contributed to the Linux kernel from a variety of
domains. Current guidance is to use some form of *.qualcomm.com, with
oss.qualcomm.com being preferred. But prior guidance was to use codeaurora.org
(up until December 2021) and quicinc.com (up until March 2025).

The current issue I see is that get_maintainer.pl can return codeaurora.org or
quicinc.com addresses in some cases (i.e. via --git-blame-signatures), and
codeaurora.org no longer accepts e-mails and quicinc.com cannot be accessed by
the engineers. And there are also cases where employees have left, and have
not established a new .mailmap entry.

So I'm wondering if there should be a mechanism in get_maintainer.pl to avoid
reporting dead domains. Or should we just enter all of the obsolete addresses
to .get_maintainer.ignore.

/jeff

Re: Should get_maintainer.pl ignore obsolete Qualcomm domains?

[Krzysztof Kozlowski]

On 10/11/2026 19:50, Jeff Johnson wrote:
> Qualcomm employees have contributed to the Linux kernel from a variety of
> domains. Current guidance is to use some form of *.qualcomm.com, with
> oss.qualcomm.com being preferred. But prior guidance was to use codeaurora.org
> (up until December 2021) and quicinc.com (up until March 2025).
> 
> The current issue I see is that get_maintainer.pl can return codeaurora.org or
> quicinc.com addresses in some cases (i.e. via --git-blame-signatures), and
> codeaurora.org no longer accepts e-mails and quicinc.com cannot be accessed by
> the engineers. And there are also cases where employees have left, and have
> not established a new .mailmap entry.
> 
> So I'm wondering if there should be a mechanism in get_maintainer.pl to avoid
> reporting dead domains. Or should we just enter all of the obsolete addresses
> to .get_maintainer.ignore.

--git-fallback takes addresses from the last year I think, so I believe
no codeaurora or quicinc woould appear thus .get_maintainer.ignore is
not a solution here. Addresses are printed (at least quicinc) because
they are listed as maintainers, e.g. for bindings or drivers (two cases
for maintainers). Obviously such bindings and drivers are abandoned,
which is a good thing to learn from the bounce.

Best regards,
Krzysztof

Re: Should get_maintainer.pl ignore obsolete Qualcomm domains?

[Krzysztof Kozlowski]

On 12/11/2026 11:10, Krzysztof Kozlowski wrote:
> On 10/11/2026 19:50, Jeff Johnson wrote:
>> Qualcomm employees have contributed to the Linux kernel from a variety of
>> domains. Current guidance is to use some form of *.qualcomm.com, with
>> oss.qualcomm.com being preferred. But prior guidance was to use codeaurora.org
>> (up until December 2021) and quicinc.com (up until March 2025).
>>
>> The current issue I see is that get_maintainer.pl can return codeaurora.org or
>> quicinc.com addresses in some cases (i.e. via --git-blame-signatures), and
>> codeaurora.org no longer accepts e-mails and quicinc.com cannot be accessed by
>> the engineers. And there are also cases where employees have left, and have
>> not established a new .mailmap entry.
>>
>> So I'm wondering if there should be a mechanism in get_maintainer.pl to avoid
>> reporting dead domains. Or should we just enter all of the obsolete addresses
>> to .get_maintainer.ignore.
> 
> --git-fallback takes addresses from the last year I think, so I believe
> no codeaurora or quicinc woould appear thus .get_maintainer.ignore is
> not a solution here. Addresses are printed (at least quicinc) because
> they are listed as maintainers, e.g. for bindings or drivers (two cases
> for maintainers). Obviously such bindings and drivers are abandoned,
> which is a good thing to learn from the bounce.
> 

I think I missed partially your point - you do not refer to
--git-fallback, but blame for fixes. Well, yes, for that I would just
drop entire @codeaurora domain. quicinc.com is still working so for me
it is litmus test if maintainer is active.

Best regards,
Krzysztof