From: David Laight <David.Laight@ACULAB.COM>
To: 'kernel test robot' <lkp@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
'Andy Shevchenko' <andriy.shevchenko@linux.intel.com>,
'Andrew Morton' <akpm@linux-foundation.org>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Christoph Hellwig <hch@infradead.org>,
"Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: "llvm@lists.linux.dev" <llvm@lists.linux.dev>,
"oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>,
"Linux Memory Management List" <linux-mm@kvack.org>
Subject: RE: [PATCH next 2/5] minmax: Allow min()/max()/clamp() if the arguments have the same signedness.
Date: Wed, 26 Jul 2023 08:30:59 +0000 [thread overview]
Message-ID: <350c7fe495424138afd15d797830c417@AcuMS.aculab.com> (raw)
In-Reply-To: <202307252359.Is4T2MXC-lkp@intel.com>
From: kernel test robot
> Sent: 25 July 2023 16:58
>
> kernel test robot noticed the following build errors:
>
...
>
> In file included from init/calibrate.c:8:
> >> include/linux/jiffies.h:427:28: error: call to undeclared function 'static_assert'; ISO C99 and
> later do not support implicit function declarations [-Wimplicit-function-declaration]
> 427 | return jiffies_to_clock_t(max(0L, delta));
> | ^
...
> include/linux/minmax.h:29:3: note: expanded from macro '__cmp_once'
> 29 | static_assert(__types_ok(x, y), \
This is fixed by the earlier patch:
[PATCH v1 1/1] minmax: Fix header inclusions
which adds #include <linux/build_bug.h> and thus defines static_assert().
Can I just assume that will be applied?
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2023-07-26 8:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <454f967d452548a9acfa7c0a0872507e@AcuMS.aculab.com>
2023-07-25 14:14 ` kernel test robot
2023-07-25 14:56 ` kernel test robot
2023-07-26 9:47 ` David Laight
2023-07-25 15:58 ` kernel test robot
2023-07-26 8:30 ` David Laight [this message]
2023-07-26 16:20 ` 'Andy Shevchenko'
2023-07-27 14:01 ` David Laight
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=350c7fe495424138afd15d797830c417@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=Jason@zx2c4.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=willy@infradead.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