All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Alexander Lobakin <alexandr.lobakin@intel.com>,
	<llvm@lists.linux.dev>, <oe-kbuild-all@lists.linux.dev>,
	<linux-kernel@vger.kernel.org>, Yury Norov <yury.norov@gmail.com>,
	kernel test robot <lkp@intel.com>
Subject: Re: lib/test_bitmap.c:920:2: error: call to __compiletime_assert_348 declared with 'error' attribute: BUILD_BUG_ON failed: !__builtin_constant_p(res)
Date: Tue, 18 Jul 2023 15:40:35 +0200	[thread overview]
Message-ID: <e05d8e00-d8cb-8c3c-fefd-3b50acb9ef31@intel.com> (raw)
In-Reply-To: <ZLUSG8bNnSqT0LO+@smile.fi.intel.com>

From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date: Mon, 17 Jul 2023 13:04:11 +0300

> On Mon, Jul 17, 2023 at 12:42:57PM +0800, kernel test robot wrote:
>> Hi Alexander,

Hi,

>>
>> FYI, the error/warning still remains.
> 
> Alexander, either you can escalate this or just propose something to discuss.
> 

Sorry, I had some days off.
I've been waiting for more info from the Clang devs to understand
whether and how I should fix this.
I see that Yury submitted fix (two actually) already, so I'll go review
it now.

Thanks,
Olek

      parent reply	other threads:[~2023-07-18 13:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-17  4:42 lib/test_bitmap.c:920:2: error: call to __compiletime_assert_348 declared with 'error' attribute: BUILD_BUG_ON failed: !__builtin_constant_p(res) kernel test robot
2023-07-17 10:04 ` Andy Shevchenko
2023-07-17 16:35   ` Nick Desaulniers
2023-07-17 18:08     ` Yury Norov
2023-07-17 18:24       ` Nick Desaulniers
2023-07-18 13:40   ` Alexander Lobakin [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=e05d8e00-d8cb-8c3c-fefd-3b50acb9ef31@intel.com \
    --to=aleksander.lobakin@intel.com \
    --cc=alexandr.lobakin@intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.