From: David Hildenbrand <david@redhat.com>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [akpm-mm:mm-unstable 175/198] WARNING: modpost: "__totalhigh_pages" [drivers/md/dm-bufio.ko] has no CRC!
Date: Wed, 12 Jun 2024 17:39:42 +0200 [thread overview]
Message-ID: <ee3d20fa-1f7e-4d45-8d71-9a5778a1391f@redhat.com> (raw)
In-Reply-To: <202406122038.Py6sGDCp-lkp@intel.com>
On 12.06.24 14:46, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-unstable
> head: 8a58962d482f5ab03d698f56fcbd5449757accfa
> commit: dae48e2d159fa9b7d6956b72cf3ebff6cd5e0de4 [175/198] mm-highmem-reimplement-totalhigh_pages-by-walking-zones-fix
> config: sparc-randconfig-001-20240612 (https://download.01.org/0day-ci/archive/20240612/202406122038.Py6sGDCp-lkp@intel.com/config)
> compiler: sparc-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240612/202406122038.Py6sGDCp-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/202406122038.Py6sGDCp-lkp@intel.com/
>
> All error/warnings (new ones prefixed by >>, old ones prefixed by <<):
That should be fixed now via the updated
"mm-highmem-reimplement-totalhigh_pages-by-walking-zones-fix".
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2024-06-12 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 12:46 kernel test robot
2024-06-12 15:39 ` David Hildenbrand [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=ee3d20fa-1f7e-4d45-8d71-9a5778a1391f@redhat.com \
--to=david@redhat.com \
--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