All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linaro-kernel@lists.linaro.org,
	Build bot for Mark Brown <broonie@kernel.org>,
	kernel-build-reports@lists.linaro.org, stable@vger.kernel.org
Subject: Re: v4.7.5 build: 0 failures 2 warnings (v4.7.5)
Date: Sun, 25 Sep 2016 17:03:26 +0200	[thread overview]
Message-ID: <20160925150326.GA14262@kroah.com> (raw)
In-Reply-To: <20160925132718.GA8415@kroah.com>


Hi Arnd,

I'm getting the following build warnings on the 4.7-stable tree, any
ideas what they are from:

In file included from ../kernel/trace/trace_irqsoff.c:15:0:
../kernel/trace/trace_irqsoff.c: In function ‘stop_critical_timings’:
../include/linux/ftrace.h:703:36: warning: calling ‘__builtin_return_address’ with a nonzero argument is unsafe [-Wframe-address]
 #  define ftrace_return_address(n) __builtin_return_address(n)
                                    ^~~~~~~~~~~~~~~~~~~~~~~~~~~
../include/linux/ftrace.h:710:38: note: in expansion of macro ‘ftrace_return_address’
 #define CALLER_ADDR1 ((unsigned long)ftrace_return_address(1))
                                      ^~~~~~~~~~~~~~~~~~~~~
../kernel/trace/trace_irqsoff.c:433:38: note: in expansion of macro ‘CALLER_ADDR1’
   stop_critical_timing(CALLER_ADDR0, CALLER_ADDR1);
                                      ^~~~~~~~~~~~

It shows up in a few other places as well with this signature.

Same goes for the 4.4-stable tree

thanks,

greg k-h

  reply	other threads:[~2016-09-25 15:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-24 13:44 v4.7.5 build: 0 failures 2 warnings (v4.7.5) Build bot for Mark Brown
2016-09-24 20:57 ` Arnd Bergmann
2016-09-25 13:27   ` Greg KH
2016-09-25 15:03     ` Greg KH [this message]
2016-09-25 23:46       ` Arnd Bergmann
2016-09-26  9:01         ` Greg KH

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=20160925150326.GA14262@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.