[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <57A4C0D3.2060408@caviumnetworks.com>
Date: Fri, 5 Aug 2016 09:37:39 -0700
From: David Daney <ddaney@...iumnetworks.com>
To: Robert Richter <robert.richter@...ium.com>
CC: <marc.zyngier@....com>, <linux@...linux.org.uk>,
<catalin.marinas@....com>, <will.deacon@....com>,
<mark.rutland@....com>, Matthias Brugger <mbrugger@...e.com>,
<kvm@...r.kernel.org>, <suzuki.poulose@....com>,
<zlim.lnx@...il.com>, <rkrcmar@...hat.com>,
<david.daney@...ium.com>, <agraf@...e.de>,
<linux-kernel@...r.kernel.org>, <ard.biesheuvel@...aro.org>,
<lorenzo.pieralisi@....com>, <james.morse@....com>,
<dave.long@...aro.org>, <pbonzini@...hat.com>,
<kvmarm@...ts.cs.columbia.edu>, <christoffer.dall@...aro.org>,
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] arm64: Add workaround for Cavium erratum 26026
On 08/05/2016 12:00 AM, Robert Richter wrote:
> On 04.08.16 14:40:48, David Daney wrote:
>> On 08/04/2016 01:57 PM, Robert Richter wrote:
>>> The patch below is on top of Matthias' patch series:
>>>
>>> arm64: Implement IPI based TLB invalidation
>>>
>>> The series is used to enable a workaround for Cavium ThunderX pass 1.x
>>> systems.
>>
>>
>> Where are the rest of the patches in the series? I would have expected
>> something like "[PATCH 1/X] arm64:..." with X being greater than one.
>
> You are cc'ed here too:
>
> https://lkml.org/lkml/2016/8/4/101
>
OK, I got confused by the fact that this patch was retroactively added
to the patch set and was missing the sequence numbering.
> -Robert
>
Powered by blists - more mailing lists