Am 19.09.2014 17:29, schrieb Jeff Kirsher:
> From: Mark Rustad <mark.d.rus...@intel.com>
>
> Silence nested-externs warnings for these, as these nested
> externs are truly wanted.
>
> CC: Oleg Nesterov <o...@redhat.com>
> CC: Andrew Morton <a...@linux-foundation.org>
> CC: Geert Uytterhoeven <ge...@linux-m68k.org>
> CC: Richard Weinberger <rich...@nod.at>
> CC: Brian Norris <computersforpe...@gmail.com>
> Signed-off-by: Mark Rustad <mark.d.rus...@intel.com>
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirs...@intel.com>
> ---
> include/linux/signal.h | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/include/linux/signal.h b/include/linux/signal.h
> index 750196f..e68ae6b 100644
> --- a/include/linux/signal.h
> +++ b/include/linux/signal.h
> @@ -67,7 +67,9 @@ static inline int sigismember(sigset_t *set, int _sig)
>
> static inline int sigisemptyset(sigset_t *set)
> {
> + DIAG_PUSH DIAG_IGNORE(nested-externs)
Do we really want to clutter the source with such tags?
Does this even build? i.e. how does gcc know to ignore that?
rw@azrael:~/linux (ubi-wlcrash $)> git grep DIAG_PUSH | wc -l
0
Thanks,
//richard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
