From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jeff Johnson <jeff.johnson@oss.qualcomm.com>, tools@kernel.org
Subject: Re: Should get_maintainer.pl ignore obsolete Qualcomm domains?
Date: Thu, 12 Nov 2026 11:10:24 +0100 [thread overview]
Message-ID: <b02133f8-4819-4615-b99d-3df8eb1aecb2@kernel.org> (raw)
In-Reply-To: <342fd0c1-671b-4487-8a42-44adecda502c@oss.qualcomm.com>
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
next prev parent reply other threads:[~2026-11-12 10:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 18:50 Should get_maintainer.pl ignore obsolete Qualcomm domains? Jeff Johnson
2026-11-12 10:10 ` Krzysztof Kozlowski [this message]
2026-11-12 10:17 ` Krzysztof Kozlowski
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=b02133f8-4819-4615-b99d-3df8eb1aecb2@kernel.org \
--to=krzk@kernel.org \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=tools@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.