[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <X7wEWQsR6N8KMzVI@kroah.com>
Date: Mon, 23 Nov 2020 19:50:01 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Nick Desaulniers <ndesaulniers@...gle.com>
Cc: Arvind Sankar <nivedita@...m.mit.edu>,
Randy Dunlap <rdunlap@...radead.org>,
LKML <linux-kernel@...r.kernel.org>,
"# 3.4.x" <stable@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Kees Cook <keescook@...omium.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Sasha Levin <sashal@...nel.org>,
Palmer Dabbelt <palmerdabbelt@...gle.com>
Subject: Re: [PATCH 5.4 044/158] compiler.h: fix barrier_data() on clang
On Mon, Nov 23, 2020 at 10:31:10AM -0800, Nick Desaulniers wrote:
> Doesn't this depend on a v2 of
> https://lore.kernel.org/lkml/fe040988-c076-8dec-8268-3fbaa8b39c0f@infradead.org/
> ? Oh, looks like v1 got picked up:
> https://lore.kernel.org/lkml/mhng-8c56f671-512a-45e7-9c94-fa39a80451da@palmerdabbelt-glaptop1/.
> Won't this break RISCV VDSO?
Oops, let me drop this, I did so in the past for 5.9.y and it looks like
Sasha missed that and added the fixed patch to 5.4.y...
thanks,
greg k-h
Powered by blists - more mailing lists