From: Petr Vorel <pvorel@suse.cz>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Mimi Zohar <zohar@linux.vnet.ibm.com>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the integrity tree
Date: Thu, 17 May 2018 11:46:24 +0200 [thread overview]
Message-ID: <20180517094624.lycmqeibd7un5ehe@dell5510> (raw)
In-Reply-To: <20180517165110.6a014e12@canb.auug.org.au>
Hi Stephen,
> Hi all,
> After merging the integrity tree, today's linux-next build (powerpc
> allyesconfig) produced this warning:
> security/integrity/ima/ima_kexec.c:18:0: warning: "pr_fmt" redefined
> #define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
> In file included from include/linux/kernel.h:14:0,
> from include/asm-generic/bug.h:18,
> from arch/powerpc/include/asm/bug.h:128,
> from include/linux/bug.h:5,
> from include/linux/seq_file.h:7,
> from security/integrity/ima/ima_kexec.c:13:
> include/linux/printk.h:288:0: note: this is the location of the previous definition
> #define pr_fmt(fmt) fmt
> Introduced by commit
> 3dea0d93d257 ("ima: Unify logging")
thanks for reporting.
Reproduced, working on fix now.
Kind regards,
Petr
next prev parent reply other threads:[~2018-05-17 9:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 6:51 linux-next: build warning after merge of the integrity tree Stephen Rothwell
2018-05-17 9:46 ` Petr Vorel [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-05 3:27 Stephen Rothwell
2021-06-07 16:48 ` Roberto Sassu
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=20180517094624.lycmqeibd7un5ehe@dell5510 \
--to=pvorel@suse.cz \
--cc=dmitry.kasatkin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=zohar@linux.vnet.ibm.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