[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wgC===Qx3STDjBWGHuzJ0SNP16gEz3iSc6Ebo_bM-yZtw@mail.gmail.com>
Date: Thu, 14 Nov 2024 09:21:31 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Huacai Chen <chenhuacai@...nel.org>
Cc: Huacai Chen <chenhuacai@...ngson.cn>, Arnd Bergmann <arnd@...db.de>, loongarch@...ts.linux.dev,
linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org,
Guo Ren <guoren@...nel.org>, Xuerui Wang <kernel@...0n.name>,
Jiaxun Yang <jiaxun.yang@...goat.com>
Subject: Re: [GIT PULL] LoongArch fixes for v6.12-final
On Wed, 13 Nov 2024 at 22:23, Huacai Chen <chenhuacai@...nel.org> wrote:
>
> Maybe the root cause is that "From" in my patch is loongson.cn but I
> use kernel.org's SMTP server?
Ahh, yes, I didn't even notice that you went through mail.kernel.org,
I only noticed that loongson.cn did SPF but not DKIM.
Yeah, if loongson had had DKIM and DMARC set up to match, it would
have been an even noisier failure about DKIM actively failing, rather
than not having DKIM at all.
If you use mail.kernel.org, using a "From:" with a kernel.org address
too to get the full email verification is likely the best option.
That said, I went back and looked, and you've clearly been using this
mail.kernel.org + loongson.cn model for a long time, and it hasn't
been problematic. So your pull request being marked as spam might have
been just a one-off.
Linus
Powered by blists - more mailing lists