From: Andrew Morton <akpm@linux-foundation.org>
To: kernel test robot <lkp@intel.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
kbuild-all@lists.01.org, Johannes Weiner <hannes@cmpxchg.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [hnaz-linux-mm:master 179/239] include/linux/thread_info.h:215:27: error: 'INT_MAX' undeclared
Date: Thu, 13 May 2021 12:08:05 -0700 [thread overview]
Message-ID: <20210513120805.14ca5439fe8a1ec2a1168d8e@linux-foundation.org> (raw)
In-Reply-To: <202105131700.z2HuiNSx-lkp@intel.com>
On Thu, 13 May 2021 17:36:14 +0800 kernel test robot <lkp@intel.com> wrote:
> tree: https://github.com/hnaz/linux-mm master
> head: 12891f829e4851b3562ddcde27a4a9ade308ada3
> commit: 161b082aa6ac5047f1b0f243f0e834d2bfb39842 [179/239] kernel.h: split out panic and oops helpers
> config: nds32-defconfig (attached as .config)
> compiler: nds32le-linux-gcc (GCC) 9.3.0
> reproduce (this is a W=1 build):
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # https://github.com/hnaz/linux-mm/commit/161b082aa6ac5047f1b0f243f0e834d2bfb39842
> git remote add hnaz-linux-mm https://github.com/hnaz/linux-mm
> git fetch --no-tags hnaz-linux-mm master
> git checkout 161b082aa6ac5047f1b0f243f0e834d2bfb39842
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross W=1 ARCH=nds32
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> Note: the hnaz-linux-mm/master HEAD 12891f829e4851b3562ddcde27a4a9ade308ada3 builds fine.
> It only hurts bisectibility.
I'm surprised. I guess some later patch accidentally fixed it.
I expect we'll see a bunch more gramlins like this. And I assume this
fixes:
--- a/include/linux/thread_info.h~kernelh-split-out-panic-and-oops-helpers-fix
+++ a/include/linux/thread_info.h
@@ -9,6 +9,7 @@
#define _LINUX_THREAD_INFO_H
#include <linux/types.h>
+#include <linux/limits.h>
#include <linux/bug.h>
#include <linux/restart_block.h>
#include <linux/errno.h>
_
next prev parent reply other threads:[~2021-05-13 19:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 9:36 [hnaz-linux-mm:master 179/239] include/linux/thread_info.h:215:27: error: 'INT_MAX' undeclared kernel test robot
2021-05-13 19:08 ` Andrew Morton [this message]
2021-05-17 9:04 ` Andy Shevchenko
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=20210513120805.14ca5439fe8a1ec2a1168d8e@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bjorn.andersson@linaro.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.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;
as well as URLs for NNTP newsgroup(s).