From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-next@vger.kernel.org, Steven Rostedt <srostedt@redhat.com>,
Alan Cox <alan@redhat.com>
Subject: Re: linux-next: ftrace tree build warnings
Date: Tue, 25 Nov 2008 10:25:15 +0000 [thread overview]
Message-ID: <20081125102515.54282c0d@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20081125133828.8f9b49df.sfr@canb.auug.org.au>
On Tue, 25 Nov 2008 13:38:28 +1100
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> Today's linux-next build (x86_64 allmodconfig) produced lots of these
> warnings:
>
> include/linux/tty.h:330: warning: '______f' is static but declared in inline function 'tty_kref_get' which is not static
>
> Caused by commit 2bcd521a684cc94befbe2ce7d5b613c841b0d304 ("trace:
> profile all if conditionals"). Something needs to be done about
> this ... maybe tty_kref_get needs to be "static inline" instead of
> "extern inline"?
If someone from the ftrace crew can sort the problem out and send me a
diff for the ttydev tree that shouldn't be a problem, but really it looks
like a problem with ftrace as that can't be the only case this happens
surely ?
next prev parent reply other threads:[~2008-11-25 10:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 2:38 linux-next: ftrace tree build warnings Stephen Rothwell
2008-11-25 2:44 ` Steven Rostedt
2008-11-25 8:00 ` Ingo Molnar
2008-11-25 8:17 ` Stephen Rothwell
2008-11-25 10:25 ` Alan Cox [this message]
2008-11-25 12:19 ` [PATCH] tracing, tty: fix warnings caused by branch tracing and tty_kref_get() Ingo Molnar
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=20081125102515.54282c0d@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=alan@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sfr@canb.auug.org.au \
--cc=srostedt@redhat.com \
--cc=tglx@linutronix.de \
/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