From: Petr Mladek <pmladek@suse.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Yafang Shao <laoar.shao@gmail.com>
Subject: Re: linux-next: Tree for Mar 10 (lib/test_printf.c)
Date: Wed, 10 Mar 2021 10:52:23 +0100 [thread overview]
Message-ID: <YEiW12IkiVothTb2@alley> (raw)
In-Reply-To: <62857b03-c12c-6841-72ae-d94f00a3a868@infradead.org>
On Tue 2021-03-09 21:57:48, Randy Dunlap wrote:
> On 3/9/21 8:02 PM, Stephen Rothwell wrote:
> > Hi all,
> >
>
> on i386 (at least):
>
> ../lib/test_printf.c: In function 'page_flags_test':
> ../lib/test_printf.c:595:17: error: 'sec' undeclared (first use in this function); did you mean 'sem'?
> page_flags |= (sec & SECTIONS_MASK) << SECTIONS_PGSHIFT;
> ^~~
>
>
> Should that be 'section'?
Yup, it looks like.
There seems to be one more problem found by the test robot:
lib/test_printf.c:595:17: note: each undeclared identifier is reported only once for each function it appears in
>> lib/test_printf.c:612:17: error: 'tag' undeclared (first use in this function)
612 | page_flags |= (tag & KASAN_TAG_MASK) << KASAN_TAG_PGSHIFT;
Yafang is going to send a fix. I have temporary removed the
problematic patch from printk/linux.git, for-next branch.
I am sorry for the troubles. Anyway, it is great that linux-next
and all the test robots are around.
Best Regards,
Petr
next prev parent reply other threads:[~2021-03-10 9:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 4:02 linux-next: Tree for Mar 10 Stephen Rothwell
2021-03-10 5:57 ` linux-next: Tree for Mar 10 (lib/test_printf.c) Randy Dunlap
2021-03-10 9:52 ` Petr Mladek [this message]
2021-03-14 8:40 ` Yafang Shao
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=YEiW12IkiVothTb2@alley \
--to=pmladek@suse.com \
--cc=laoar.shao@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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