mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Brian Norris <briannorris@chromium.org>
Cc: Yury Norov <yury.norov@gmail.com>,
	llvm@lists.linux.dev, linux-kernel@vger.kernel.org,
	Bill Wendling <morbo@google.com>,
	Justin Stitt <justinstitt@google.com>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	Kees Cook <kees@kernel.org>
Subject: Re: [PATCH v2] bitmap: Switch from inline to __always_inline
Date: Sat, 13 Jul 2024 16:27:05 -0700	[thread overview]
Message-ID: <20240713232705.GA443207@thelio-3990X> (raw)
In-Reply-To: <ZpGVLl7NQZScd8aH@google.com>

Hi Brian,

On Fri, Jul 12, 2024 at 01:42:22PM -0700, Brian Norris wrote:
> But agreed, I can get a larger matrix with a bit more specifity in my
> commit log. TBD on the ease of getting a Clang 13 or GCC 9 toolchain,
> but I think I can convince my distro to provide them.

In case you have not seen them already, there are GCC and LLVM
toolchains available on kernel.org to make doing this type of testing
easier:

https://mirrors.edge.kernel.org/pub/tools/crosstool
https://mirrors.edge.kernel.org/pub/tools/llvm

Then use either

  CROSS_COMPILE=<install_prefix>/bin/x86_64-linux-

or

  LLVM=<install_prefix>/bin/

when building your kernels. If you have any issues with them, just let
me know and I'll try to help out.

Cheers,
Nathan

      parent reply	other threads:[~2024-07-13 23:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-11 16:37 Brian Norris
2024-07-12 17:02 ` Yury Norov
2024-07-12 18:01   ` Kees Cook
2024-07-12 23:54     ` Yury Norov
2024-07-12 20:42   ` Brian Norris
2024-07-13  0:19     ` Yury Norov
2024-07-13 23:27     ` Nathan Chancellor [this message]

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=20240713232705.GA443207@thelio-3990X \
    --to=nathan@kernel.org \
    --cc=briannorris@chromium.org \
    --cc=justinstitt@google.com \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=llvm@lists.linux.dev \
    --cc=morbo@google.com \
    --cc=ndesaulniers@google.com \
    --cc=yury.norov@gmail.com \
    /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
all inboxes | Powered by JetHome®