From: Sascha Hauer <s.hauer@pengutronix.de>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 0/3] fix "no previous prototype" warnings
Date: Mon, 20 Mar 2017 09:05:31 +0100 [thread overview]
Message-ID: <20170320080531.nm6n25gsvqe3qk2k@pengutronix.de> (raw)
In-Reply-To: <20170320065954.8330-1-antonynpavlov@gmail.com>
On Mon, Mar 20, 2017 at 09:59:51AM +0300, Antony Pavlov wrote:
> Antony Pavlov (3):
> gui: bmp.c: fix "no previous prototype" warning
> clk: clk-gate-shared: fix "no previous prototype" warning
> gui: image_renderer: fix "no previous prototype for
> 'image_renderer_unregister'" warning
Applied, thanks
I notice we currently have -Wmissing-prototypes only on Mips. Maybe we
should enable this on other architectures aswell to make these warnings
more visible.
On ARM though we have tons of missing prototypes, so we should fix a
fair amount of them before enabling this warning in the tree.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2017-03-20 8:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 6:59 Antony Pavlov
2017-03-20 6:59 ` [PATCH 1/3] gui: bmp.c: fix "no previous prototype" warning Antony Pavlov
2017-03-20 6:59 ` [PATCH 2/3] clk: clk-gate-shared: " Antony Pavlov
2017-03-20 6:59 ` [PATCH 3/3] gui: image_renderer: fix "no previous prototype for 'image_renderer_unregister'" warning Antony Pavlov
2017-03-20 8:05 ` Sascha Hauer [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=20170320080531.nm6n25gsvqe3qk2k@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.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