From: Lorenzo Stoakes <lorenzo.stoakes@oracle.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>,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [akpm-mm:mm-unstable 106/111] include/linux/kern_levels.h:5:25: warning: unknown conversion type character 'b' in format
Date: Fri, 31 Jan 2025 12:27:45 +0000 [thread overview]
Message-ID: <eac8bc02-685e-4a9f-bee5-9d245b3f29b0@lucifer.local> (raw)
In-Reply-To: <4b879d9a-2d38-4788-9475-b81ae34eb886@lucifer.local>
On Fri, Jan 31, 2025 at 10:07:59AM +0000, Lorenzo Stoakes wrote:
> On Fri, Jan 31, 2025 at 05:43:28PM +0800, kernel test robot wrote:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-unstable
> > head: f5604ad70091eabe663ea7106ced99449d653320
> > commit: 951452b2ec82d352a69f14cfffdeb7c08461eefb [106/111] mm: further refactor commit_merge()
> > config: x86_64-buildonly-randconfig-001-20250131 (https://download.01.org/0day-ci/archive/20250131/202501311708.dRI35epU-lkp@intel.com/config)
> > compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250131/202501311708.dRI35epU-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/202501311708.dRI35epU-lkp@intel.com/
> >
> > All warnings (new ones prefixed by >>):
> >
> > In file included from include/linux/kernel.h:31,
> > from mm/debug.c:9:
> > mm/debug.c: In function 'dump_vmg':
> > >> include/linux/kern_levels.h:5:25: warning: unknown conversion type character 'b' in format [-Wformat=]
> > 5 | #define KERN_SOH "\001" /* ASCII Start Of Header */
>
> Well that'll teach me for assuming a compiler with CONFIG_WERROR on will
> actually... report warnings as errors. Apparently not.
>
> Will send a follow up fix-patch...
>
Even a W=1 build doesn't pick this up, so I'm thinking this might be a
compiler version thing.
Am doing a respin as that'll be easier.
prev parent reply other threads:[~2025-01-31 12:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 9:43 kernel test robot
2025-01-31 10:07 ` Lorenzo Stoakes
2025-01-31 12:27 ` Lorenzo Stoakes [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=eac8bc02-685e-4a9f-bee5-9d245b3f29b0@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vbabka@suse.cz \
/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