From: Linus Torvalds <torvalds@linux-foundation.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
tglx@linutronix.de, Greg KH <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] scheduler updates for v4.20
Date: Tue, 23 Oct 2018 15:12:22 +0100 [thread overview]
Message-ID: <CAHk-=wgAA7jjZRm1nixAWDYgcRf6rkR9X-xMEwhU8+T1F-+XMg@mail.gmail.com> (raw)
In-Reply-To: <20181023110600.GA43785@gmail.com>
On Tue, Oct 23, 2018 at 12:06 PM Ingo Molnar <mingo@kernel.org> wrote:
>
> Please pull the latest sched-core-for-linus git tree from:
Hmm. I've pulled, but this message was odd and mis-formed.
First off, it didn't have a diffstat (I did verify the shortlog instead).
Secondly, can you please check how you send emails. I get a DMARC
failure on that email, looking like this:
ARC-Authentication-Results: i=1; mx.google.com;
dkim=pass header.i=@gmail.com header.s=20161025 header.b=iFVXLHcJ;
spf=pass (google.com: domain of mingo.kernel.org@gmail.com
designates 209.85.220.65 as permitted sender)
smtp.mailfrom=mingo.kernel.org@gmail.com;
dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org
so it seems something is unhappy with how you had that
Sender: Ingo Molnar <mingo.kernel.org@gmail.com>
From: Ingo Molnar <mingo@kernel.org>
set up. It looks like you went directly through gmail rather than
going through kernel.org and getting a proper kernel.org dkim hash.
Thirdly (and least importantly), you should probably check your MUA
(which seems to be Mutt), because this came in with
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
and using iso-8859-1 instead of utf-8 in this day and age is just all
kinds of odd. It looks like it was all fine, but if Mutt has an
option to just send as utf-8, I encourae everybody to just use that
and try to just have utf-8 everywhere. We've had too many silly issues
when people mix locales etc and some point in the chain gets it
wrong..
Linus
prev parent reply other threads:[~2018-10-23 14:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 11:06 [GIT PULL] scheduler updates for v4.20 Ingo Molnar
2018-10-23 14:12 ` Linus Torvalds [this message]
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='CAHk-=wgAA7jjZRm1nixAWDYgcRf6rkR9X-xMEwhU8+T1F-+XMg@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).