From: Li Zefan <lizf@cn.fujitsu.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Peter Zijlstra <peterz@infradead.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH] perf: Mark perf_data_size() inline
Date: Thu, 18 Aug 2011 10:24:16 +0800 [thread overview]
Message-ID: <4E4C77D0.4020601@cn.fujitsu.com> (raw)
Otherwise we'll get compile warning if internal.h is included but
perf_data_size() is not used.
Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
---
kernel/events/internal.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/kernel/events/internal.h b/kernel/events/internal.h
index 09097dd..a318056 100644
--- a/kernel/events/internal.h
+++ b/kernel/events/internal.h
@@ -64,7 +64,7 @@ static inline int page_order(struct ring_buffer *rb)
}
#endif
-static unsigned long perf_data_size(struct ring_buffer *rb)
+static inline unsigned long perf_data_size(struct ring_buffer *rb)
{
return rb->nr_pages << (PAGE_SHIFT + page_order(rb));
}
--
1.7.3.1
reply other threads:[~2011-08-18 2:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4E4C77D0.4020601@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@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