From: Borislav Petkov <bp@alien8.de>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: bp@suse.de, richard@nod.at,
Masahiro Yamada <yamada.masahiro@socionext.com>,
mingo@redhat.com, LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, hpa@zytor.com, jdike@addtoit.com,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/build] x86/um/vdso: Drop implicit common-page-size linker flag
Date: Tue, 11 Dec 2018 21:53:53 +0100 [thread overview]
Message-ID: <20181211205353.GR27375@zn.tnic> (raw)
In-Reply-To: <CAKwvOd=OY-qWqxK9gcacKChAEAPqFWyyBbgsQK6-h0zTYTcOgg@mail.gmail.com>
On Tue, Dec 11, 2018 at 11:08:30AM -0800, Nick Desaulniers wrote:
> Personal gmail account, yes. Corporate gmail, no, IIUC. There was a
> pretty big internal thread where all of our kernel contributors got
> cut off one day and were scrambling to figure out how to send/review
> patches as their workflows were interrupted.
Gotta love all those stories of kernel people and corporate mail
systems... And every company has its own strange idiosyncrasies...
> Something is still not configured right when I send patches
> (maintainers have merged patches with my email address but no name, I
> assume from working with mbox files).
Yeah, had to fix that up today too. For some reason your git setup
X-Mailer: git-send-email 2.20.0.rc2.403.gdbc3b29805-goog
doesn't do names in From:
https://lkml.kernel.org/r/20181210222718.19926-1-ndesaulniers@google.com
> We have some internal tool that's smtp based but does the two factor
> authentication.
So some people send from !corporate mail servers but put their company's
name in brackets to keep attribution:
Signed-off-by: <First name> <Last name> (<Company>) <email@address.com>
For example. Dunno if that's something that would make sense for your
case though.
> Internal Gmail developers were able to help me verify that SPF was
> setup correctly, but indeed there's no DKIM. This article has more
> info: https://support.google.com/mail/answer/81126?hl=en.
I know that one from my very recent past. :)
> Richard, I don't know if that's a lot of work on your end, but other
> folks using gmail might have the same issue repeatedly with receiving
> emails from your domain otherwise.
We had to do that too for our domain.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2018-12-11 20:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 19:12 [PATCH] x86/vdso: drop implicit common-page-size linker flag ndesaulniers
2018-12-06 20:29 ` Andy Lutomirski
2018-12-07 10:18 ` Borislav Petkov
2018-12-07 17:45 ` Nick Desaulniers
2018-12-07 17:52 ` Borislav Petkov
2018-12-07 18:00 ` Nick Desaulniers
2018-12-07 18:33 ` [tip:x86/urgent] x86/vdso: Drop " tip-bot for Nick Desaulniers
2018-12-11 13:12 ` [tip:x86/build] x86/um/vdso: " tip-bot for ndesaulniers@google.com
2018-12-11 17:39 ` Nick Desaulniers
2018-12-11 17:43 ` Richard Weinberger
2018-12-11 17:46 ` Borislav Petkov
2018-12-11 17:53 ` Nick Desaulniers
2018-12-11 18:05 ` Borislav Petkov
2018-12-11 19:08 ` Nick Desaulniers
2018-12-11 20:14 ` Richard Weinberger
2018-12-11 20:53 ` Borislav Petkov [this message]
2018-12-11 13:25 ` tip-bot for Nick Desaulniers
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=20181211205353.GR27375@zn.tnic \
--to=bp@alien8.de \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=ndesaulniers@google.com \
--cc=richard@nod.at \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yamada.masahiro@socionext.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox