Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
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
In-Reply-To: <BBA90891-8A4A-4A39-BF51-13EECDE414F1@amazon.com>
References: <BBA90891-8A4A-4A39-BF51-13EECDE414F1@amazon.com>
Date:   Fri, 17 Jul 2020 23:23:04 +0200
Message-ID: <87blkdrg3r.fsf@nanos.tec.linutronix.de>
MIME-Version: 1.0
Content-Type: text/plain
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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