From: Christoph Hellwig <hch@infradead.org>
To: Palmer Dabbelt <palmer@sifive.com>
Cc: Christoph Hellwig <hch@infradead.org>,
linux@roeck-us.net, aou@eecs.berkeley.edu,
Andrew Waterman <andrew@sifive.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, linux@dominikbrodowski.net,
Marcus Comstedt <marcus@mc.pp.se>,
tklauser@distanz.ch, linux-riscv@lists.infradead.org,
dan.carpenter@oracle.com
Subject: Re: [PATCH v3 2/2] RISC-V: Don't use a global include guard for uapi/asm/syscalls.h
Date: Tue, 14 Aug 2018 06:40:27 -0700 [thread overview]
Message-ID: <20180814134027.GD28080@infradead.org> (raw)
In-Reply-To: <20180809221952.24260-3-palmer@sifive.com>
> index 818655b0d535..690beb002d1d 100644
> --- a/arch/riscv/include/uapi/asm/syscalls.h
> +++ b/arch/riscv/include/uapi/asm/syscalls.h
> @@ -1,10 +1,13 @@
> -/* SPDX-License-Identifier: GPL-2.0 */
> +// SPDX-License-Identifier: GPL-2.0
/* ... */ is the right style SPDX tag for headers, so please keep it
as-is.
next prev parent reply other threads:[~2018-08-14 13:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 22:19 RISC-V: Don't use a global include guard for uapi/asm/syscalls Palmer Dabbelt
2018-08-09 22:19 ` [PATCH v3 1/2] RISC-V: Define sys_riscv_flush_icache when SMP=n Palmer Dabbelt
2018-08-10 8:38 ` Christoph Hellwig
2018-08-10 18:27 ` Palmer Dabbelt
2018-08-10 18:47 ` Guenter Roeck
2018-08-10 20:55 ` Palmer Dabbelt
2018-08-14 13:35 ` Christoph Hellwig
2018-08-10 14:07 ` Guenter Roeck
2018-08-14 13:39 ` Christoph Hellwig
2018-08-20 23:30 ` Palmer Dabbelt
2018-08-09 22:19 ` [PATCH v3 2/2] RISC-V: Don't use a global include guard for uapi/asm/syscalls.h Palmer Dabbelt
2018-08-10 14:07 ` Guenter Roeck
2018-08-14 13:40 ` Christoph Hellwig [this message]
2018-08-20 23:30 ` Palmer Dabbelt
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=20180814134027.GD28080@infradead.org \
--to=hch@infradead.org \
--cc=andrew@sifive.com \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=dan.carpenter@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@dominikbrodowski.net \
--cc=linux@roeck-us.net \
--cc=marcus@mc.pp.se \
--cc=palmer@sifive.com \
--cc=tklauser@distanz.ch \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).