From: Joe Perches <joe@perches.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powernv: Use __printf in pe_level_printk
Date: Thu, 14 Jul 2016 21:59:12 -0700 [thread overview]
Message-ID: <1468558752.8745.52.camel@perches.com> (raw)
In-Reply-To: <87eg6vbjr2.fsf@@concordia.ellerman.id.au>
On Fri, 2016-07-15 at 14:36 +1000, Michael Ellerman wrote:
> Joe Perches <joe@perches.com> writes:
>
> >
> > Make the compiler detect format and argument mismatches.
> >
> > Signed-off-by: Joe Perches <joe@perches.com>
> > ---
> > arch/powerpc/platforms/powernv/pci.h | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/arch/powerpc/platforms/powernv/pci.h
> > b/arch/powerpc/platforms/powernv/pci.h
> > index 3a97990..1c1a586 100644
> > --- a/arch/powerpc/platforms/powernv/pci.h
> > +++ b/arch/powerpc/platforms/powernv/pci.h
> > @@ -213,6 +213,7 @@ extern void pnv_pci_dma_bus_setup(struct pci_bus
> > *bus);
> > extern int pnv_setup_msi_irqs(struct pci_dev *pdev, int nvec, int
> > type);
> > extern void pnv_teardown_msi_irqs(struct pci_dev *pdev);
> >
> > +__printf(3, 4)
> > extern void pe_level_printk(const struct pnv_ioda_pe *pe, const
> > char *level,
> > const char *fmt, ...);
> Thanks, but it breaks the build due to lots of new warnings.
>
> We'll have to fix those before merging it.
Good. Are you going to fix those?
I thought I did a powerpc defconfig build of arch/powerpc/
and I believe it finished without error, but I'm pleased
it found some defects.
I think it's now marked "rejected" in patchwork.
Perhaps it'd better to mark it "deferred" instead.
next prev parent reply other threads:[~2016-07-15 4:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 15:45 [PATCH] powernv: Use __printf in pe_level_printk Joe Perches
[not found] ` <87eg6vbjr2.fsf@@concordia.ellerman.id.au>
2016-07-15 4:59 ` Joe Perches [this message]
2016-07-22 5:34 ` kbuild test robot
2016-07-22 7:45 ` kbuild test robot
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=1468558752.8745.52.camel@perches.com \
--to=joe@perches.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
/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