@krzk I got the same thing sent to my @kernel.org address and at least three other addresses I'm sure I never gave them, including one that only showed up by accident as the committer (not author or S-o-b) ID in some kernel commits back in 2007. The only other emails I ever received there are low-quality phishing attempts.
I found one earlier email sent to the @kernel.org one, dated July 31, Subject "The KubeCon + CloudNativeCon North America 2025 Schedule Is Live!".
@krzk Now you made me aware, I checked, and I also received that email on a contrived address I briefly used for sending kernel patches more than a decade ago!
FTR, the form also didn't work when they had secretly subscribed me to the Hyperledger newsletter 7y ago... My complaint emails were never acknowledged, but the second one did seem to have the intended effect.
And pasting here my response for reference:
Thank you for responding and caring about this matter. It partially resolves the problem, but unfortunately only partially.
Email address of EU individual, like me or few other maintainers who confirmed that they received mentioned PyTorch Foundation mailing, is personal data thus protected by GDPR. Public availability of that address does not remove GDPR protection.
Therefore according to GDPR, neither the PyTorch Foundation, the Linux Foundation EU nor the Linux Foundation, was allowed to create the “list intended for technical cross-referencing”. You cannot harvest these emails, even if you do not intend to send advertising material.
Removal of harvested emails from marketing databases is of course correct, but insufficient. Linux Foundation and PyTorch Foundation should remove ALL HARVESTED emails from all other databases, including from the “list intended for technical cross-referencing”.
GDPR applies not only to Linux Foundation EU, but also to PyTorch Foundation which operates in EU. Specifically, the advertisement spam sent by PyTorch Foundation was about conference “PyTorchCon Europe 2026” it held/is holding in Paris, France. thus clearly it operated in EU. The emails were belonging to identifiable individual (e.g. me) and EU residents (e.g. also me), thus meeting all conditions necessary to trigger GDPR protection of personal data.
@krzk How else did you think these fancy graphs and statistics in LF Reports are created? From cross-referenced data extracted from git repos, of course.