From: tip-bot for Baruch Siach <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, paulus@samba.org, hpa@zytor.com,
mingo@kernel.org, a.p.zijlstra@chello.nl,
acme@ghostprotocols.net, baruch@tkos.co.il, tglx@linutronix.de
Subject: [tip:perf/urgent] perf/doc: Remove mention of non-existent set_perf_event_pending() from design.txt
Date: Sun, 26 Jan 2014 01:15:31 -0800 [thread overview]
Message-ID: <tip-0d4dd797564cddc1f71ab0b239e9ea50ddd40b2a@git.kernel.org> (raw)
In-Reply-To: <4c54761865d40210be0628cb84701afc5d57b5d8.1390686193.git.baruch@tkos.co.il>
Commit-ID: 0d4dd797564cddc1f71ab0b239e9ea50ddd40b2a
Gitweb: http://git.kernel.org/tip/0d4dd797564cddc1f71ab0b239e9ea50ddd40b2a
Author: Baruch Siach <baruch@tkos.co.il>
AuthorDate: Sat, 25 Jan 2014 23:50:23 +0200
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Sun, 26 Jan 2014 09:37:48 +0100
perf/doc: Remove mention of non-existent set_perf_event_pending() from design.txt
set_perf_event_pending() was removed in e360adbe ("irq_work: Add
generic hardirq context callbacks").
Signed-off-by: Baruch Siach <baruch@tkos.co.il>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Link: http://lkml.kernel.org/r/4c54761865d40210be0628cb84701afc5d57b5d8.1390686193.git.baruch@tkos.co.il
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
tools/perf/design.txt | 1 -
1 file changed, 1 deletion(-)
diff --git a/tools/perf/design.txt b/tools/perf/design.txt
index 67e5d0c..63a0e6f 100644
--- a/tools/perf/design.txt
+++ b/tools/perf/design.txt
@@ -454,7 +454,6 @@ So to start with, in order to add HAVE_PERF_EVENTS to your Kconfig, you
will need at least this:
- asm/perf_event.h - a basic stub will suffice at first
- support for atomic64 types (and associated helper functions)
- - set_perf_event_pending() implemented
If your architecture does have hardware capabilities, you can override the
weak stub hw_perf_event_init() to register hardware counters.
prev parent reply other threads:[~2014-01-26 9:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-25 21:50 [PATCH RESEND] perf: design.txt: remove mention of set_perf_event_pending Baruch Siach
2014-01-26 9:15 ` tip-bot for Baruch Siach [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=tip-0d4dd797564cddc1f71ab0b239e9ea50ddd40b2a@git.kernel.org \
--to=tipbot@zytor.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=baruch@tkos.co.il \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulus@samba.org \
--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
all inboxes | Powered by JetHome®