From: Thomas Gleixner <tglx@linutronix.de>
To: "Saidi\, Ali" <alisaidi@amazon.com>, LKML <linux-kernel@vger.kernel.org>
Cc: "x86\@kernel.org" <x86@kernel.org>, "Herrenschmidt\,
Benjamin" <benh@amazon.com>, Ali Saidi <aliaidi@amazon.com>,
Marc Zyngier <maz@kernel.org>,
"linux-arm-kernel\@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] genirq/affinity: Handle affinity setting on inactive interrupts correctly
Date: Fri, 17 Jul 2020 23:23:04 +0200 [thread overview]
Message-ID: <87blkdrg3r.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <BBA90891-8A4A-4A39-BF51-13EECDE414F1@amazon.com>
Ali,
"Saidi, Ali" <alisaidi@amazon.com> writes:
can you pretty please fix your mail setup. Your replies lack the
following headers:
In-Reply-To:
References:
but carry some useless Microsoft gunk instead:
Thread-Topic: [PATCH] genirq/affinity: Handle affinity setting on inactive
interrupts correctly
Thread-Index: AQHWXE5yOF+Kj67jZUWJl7gBhLLD9A==
which is non RFC and not documented. Evolution has some magic hack to
decode this mess, but all mail readers which rely on the documented RFC
fields including archives:
https://lore.kernel.org/lkml/BBA90891-8A4A-4A39-BF51-13EECDE414F1@amazon.com/
fail to properly thread your mails. That sucks.
> Tested on an arm64 system that originally experienced the issue and couldn't reproduce it with this patch.
> Tested-by: Ali Saidi <alisaidi@amazon.com>
Nevertheless, thanks for confirming that it solves the problem :)
tglx
next prev parent reply other threads:[~2020-07-17 21:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 15:25 [PATCH] genirq/affinity: Handle affinity setting on inactive interrupts correctly Saidi, Ali
2020-07-17 21:23 ` Thomas Gleixner [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-07-17 13:14 Thomas Gleixner
2020-07-17 15:25 ` kernel test robot
2020-07-17 18:04 ` kernel test robot
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=87blkdrg3r.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=aliaidi@amazon.com \
--cc=alisaidi@amazon.com \
--cc=benh@amazon.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox