[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190523102357.GB3370@lakrids.cambridge.arm.com>
Date: Thu, 23 May 2019 11:23:57 +0100
From: Mark Rutland <mark.rutland@....com>
To: Palmer Dabbelt <palmer@...ive.com>
Cc: linux-kernel@...r.kernel.org, peterz@...radead.org,
Will Deacon <will.deacon@....com>, aou@...s.berkeley.edu,
Arnd Bergmann <arnd@...db.de>, bp@...en8.de,
catalin.marinas@....com, davem@...emloft.net, fenghua.yu@...el.com,
heiko.carstens@...ibm.com, herbert@...dor.apana.org.au,
ink@...assic.park.msu.ru, jhogan@...nel.org, linux@...linux.org.uk,
mattst88@...il.com, mingo@...nel.org, mpe@...erman.id.au,
paul.burton@...s.com, paulus@...ba.org, ralf@...ux-mips.org,
rth@...ddle.net, stable@...r.kernel.org, tglx@...utronix.de,
tony.luck@...el.com, vgupta@...opsys.com
Subject: Re: [PATCH 12/18] locking/atomic: riscv: use s64 for atomic64
On Wed, May 22, 2019 at 12:06:31PM -0700, Palmer Dabbelt wrote:
> On Wed, 22 May 2019 06:22:44 PDT (-0700), mark.rutland@....com wrote:
> > As a step towards making the atomic64 API use consistent types treewide,
> > let's have the s390 atomic64 implementation use s64 as the underlying
>
> and apparently the RISC-V one as well? :)
Heh. You can guess which commit message I wrote first...
> Reviwed-by: Palmer Dabbelt <palmer@...ive.com>
Cheers! I'll add an extra 'e' when I fold this in. :)
Thanks,
Mark.
Powered by blists - more mailing lists