From: Matthew Wilcox <willy@infradead.org>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [linux-next:master 8002/8441] include/linux/compiler_types.h:397:45: error: call to '__compiletime_assert_324' declared with attribute error: BUILD_BUG_ON failed: IS_ENABLED(CONFIG_32BIT) && (PFN_PTE_SHIFT > PAGE_SHIFT)
Date: Tue, 15 Aug 2023 03:30:30 +0100 [thread overview]
Message-ID: <ZNrjRmlEbseKFdIq@casper.infradead.org> (raw)
In-Reply-To: <202308150902.iqtQSoIb-lkp@intel.com>
On Tue, Aug 15, 2023 at 09:44:02AM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 21ef7b1e17d039053edaeaf41142423810572741
> commit: 8d670cfbf3be95bbf2cb7ecdd8f449aabde8c182 [8002/8441] mips: implement the new page table range API
> config: mips-randconfig-r002-20230815 (https://download.01.org/0day-ci/archive/20230815/202308150902.iqtQSoIb-lkp@intel.com/config)
> compiler: mipsel-linux-gcc (GCC) 12.3.0
> reproduce: (https://download.01.org/0day-ci/archive/20230815/202308150902.iqtQSoIb-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202308150902.iqtQSoIb-lkp@intel.com/
How do I get you to stop reporting this? As I've said twice before now,
I did not create this warning, I simply changed some things which caused
the warning to change.
next prev parent reply other threads:[~2023-08-15 2:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 1:44 kernel test robot
2023-08-15 2:30 ` Matthew Wilcox [this message]
2023-08-15 3:09 ` Liu, Yujie
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=ZNrjRmlEbseKFdIq@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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