From: Andreas Schwab <schwab@linux-m68k.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
linux-kernel@vger.kernel.org, clang-built-linux@googlegroups.com,
Arvind Sankar <nivedita@alum.mit.edu>,
Nathan Chancellor <natechancellor@gmail.com>,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH] compiler.h: Fix barrier_data() on clang
Date: Mon, 16 Nov 2020 19:30:44 +0100 [thread overview]
Message-ID: <87k0ul9msr.fsf@igel.home> (raw)
In-Reply-To: <0dbaca2d-9ad0-8c1a-a280-97be01cac2bd@infradead.org> (Randy Dunlap's message of "Mon, 16 Nov 2020 09:53:46 -0800")
On Nov 16 2020, Randy Dunlap wrote:
> What kernel version are you building?
5.10-rc4
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Andreas Schwab <schwab@linux-m68k.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Arvind Sankar <nivedita@alum.mit.edu>,
Nathan Chancellor <natechancellor@gmail.com>,
Nick Desaulniers <ndesaulniers@google.com>,
clang-built-linux@googlegroups.com, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH] compiler.h: Fix barrier_data() on clang
Date: Mon, 16 Nov 2020 19:30:44 +0100 [thread overview]
Message-ID: <87k0ul9msr.fsf@igel.home> (raw)
In-Reply-To: <0dbaca2d-9ad0-8c1a-a280-97be01cac2bd@infradead.org> (Randy Dunlap's message of "Mon, 16 Nov 2020 09:53:46 -0800")
On Nov 16 2020, Randy Dunlap wrote:
> What kernel version are you building?
5.10-rc4
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2020-11-16 18:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 21:26 [PATCH] compiler.h: Fix barrier_data() on clang Arvind Sankar
2020-10-14 22:51 ` Nick Desaulniers
2020-10-15 8:50 ` David Laight
2020-10-15 14:45 ` Arvind Sankar
2020-10-15 15:24 ` David Laight
2020-10-15 15:39 ` Arvind Sankar
2020-10-15 17:39 ` Nick Desaulniers
2020-10-15 18:13 ` [PATCH] compiler.h: Clarify comment about the need for barrier_data() Arvind Sankar
2020-10-15 18:25 ` Nick Desaulniers
2020-10-15 21:09 ` David Laight
2020-10-15 22:01 ` Arvind Sankar
2020-10-16 8:13 ` David Laight
2020-10-16 13:09 ` Arvind Sankar
2020-10-21 19:46 ` [PATCH] compiler.h: Fix barrier_data() on clang Kees Cook
2020-11-16 17:47 ` Andreas Schwab
2020-11-16 17:47 ` Andreas Schwab
2020-11-16 17:53 ` Randy Dunlap
2020-11-16 17:53 ` Randy Dunlap
2020-11-16 18:30 ` Andreas Schwab [this message]
2020-11-16 18:30 ` Andreas Schwab
2020-11-16 19:28 ` Randy Dunlap
2020-11-16 19:28 ` Randy Dunlap
2020-11-16 22:19 ` Randy Dunlap
2020-11-16 22:19 ` Randy Dunlap
2020-11-16 19:31 ` Nick Desaulniers
2020-11-16 19:31 ` Nick Desaulniers
2020-11-16 21:07 ` Andreas Schwab
2020-11-16 21:07 ` Andreas Schwab
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=87k0ul9msr.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=nivedita@alum.mit.edu \
--cc=rdunlap@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.