From: Peter Zijlstra <peterz@infradead.org>
To: ndesaulniers@google.com
Cc: "Borislav Petkov (AMD)" <bp@alien8.de>,
Josh Poimboeuf <jpoimboe@kernel.org>,
x86@kernel.org, Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Miguel Ojeda <ojeda@kernel.org>,
Nathan Chancellor <nathan@kernel.org>, Tom Rix <trix@redhat.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH 0/2] start_kernel: omit stack canary
Date: Thu, 13 Apr 2023 09:51:06 +0200 [thread overview]
Message-ID: <20230413075106.GE4253@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20230412-no_stackp-v1-0-46a69b507a4b@google.com>
On Wed, Apr 12, 2023 at 11:32:11AM -0700, ndesaulniers@google.com wrote:
> Nick Desaulniers (2):
> start_kernel: add no_stack_protector fn attr
> start_kernel: omit prevent_tail_call_optimization for newer toolchains
>
Your second patch has a vile comment style :-)
Other than that,
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
next prev parent reply other threads:[~2023-04-13 7:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 18:32 [PATCH 0/2] start_kernel: omit stack canary ndesaulniers
2023-04-12 18:32 ` [PATCH 1/2] start_kernel: add no_stack_protector fn attr ndesaulniers
2023-04-12 20:22 ` Miguel Ojeda
2023-04-12 22:03 ` Nathan Chancellor
2023-04-14 0:09 ` Michael Ellerman
2023-04-12 18:32 ` [PATCH 2/2] start_kernel: omit prevent_tail_call_optimization for newer toolchains ndesaulniers
2023-04-12 22:04 ` Nathan Chancellor
2023-04-13 7:51 ` Peter Zijlstra [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-17 21:54 [PATCH 0/2] start_kernel: omit stack canary ndesaulniers
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=20230413075106.GE4253@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=christophe.leroy@csgroup.eu \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=llvm@lists.linux.dev \
--cc=mpe@ellerman.id.au \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=npiggin@gmail.com \
--cc=ojeda@kernel.org \
--cc=trix@redhat.com \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox