Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: Yury Norov <yury.norov@gmail.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
	linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Alexander Lobakin <alexandr.lobakin@intel.com>,
	Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	Tom Rix <trix@redhat.com>,
	oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH] lib/bitmap: waive const_eval test as it breaks the build
Date: Mon, 17 Jul 2023 15:06:23 -0700	[thread overview]
Message-ID: <ZLW7X04wQ1b9jdHZ@yury-ThinkPad> (raw)
In-Reply-To: <20230717215328.GA18505@dev-arch.thelio-3990X>

> > > Yury, Nathan,
> > > Thanks for the patches and discussion.  Yes, I think a combo of:
> > > 
> > > 1. Nathan's lib/Makefile change plus
> > > 2. Yury's removal of the current preprocessor guards in lib/test_bitmap.c
> > > 
> > > make most sense.
> > 
> > OK, then I'll send a v2 shortly. Nathan, don't you mind if I add your
> > co-developed-by for this?
> 
> Sure, no worries!
> 
> Co-developed-by: Nathan Chancellor <nathan@kernel.org>
> Signed-off-by: Nathan Chancellor <nathan@kernel.org>

Done. Just removed external link from Makefile. We've got it in commit
message anyways, so better to not pollute sources.

      reply	other threads:[~2023-07-17 22:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-17 19:58 [PATCH] lib/bitmap: waive const_eval test as it breaks the build Yury Norov
2023-07-17 20:31 ` Nathan Chancellor
2023-07-17 20:57   ` Nick Desaulniers
2023-07-17 21:31     ` Yury Norov
2023-07-17 21:53       ` Nathan Chancellor
2023-07-17 22:06         ` Yury Norov [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=ZLW7X04wQ1b9jdHZ@yury-ThinkPad \
    --to=yury.norov@gmail.com \
    --cc=alexandr.lobakin@intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=llvm@lists.linux.dev \
    --cc=maxim.kuvyrkov@linaro.org \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=trix@redhat.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