[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87v8bn3pgz.fsf@all.your.base.are.belong.to.us>
Date: Wed, 04 Oct 2023 07:51:08 +0200
From: Björn Töpel <bjorn@...nel.org>
To: Alexandre Ghiti <alexghiti@...osinc.com>,
Steven Rostedt <rostedt@...dmis.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>,
Sami Tolvanen <samitolvanen@...gle.com>,
Kees Cook <keescook@...omium.org>,
linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org,
linux-riscv@...ts.infradead.org, Conor Dooley <conor@...nel.org>,
Conor Dooley <conor.dooley@...rochip.com>
Subject: Re: [PATCH -fixes] riscv: Fix ftrace syscall handling which are now
prefixed with __riscv_
Alexandre Ghiti <alexghiti@...osinc.com> writes:
> @Conor Dooley This fails checkpatch but the documentation here states
> that this is how to do:
> https://elixir.bootlin.com/linux/latest/source/Documentation/trace/ftrace-design.rst#L246
FWIW, I'll relax the PW CI checkpatch test going forward. It's way too
strict...
Powered by blists - more mailing lists