From: Anton Blanchard <anton@samba.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: davem@davemloft.net, peterz@infradead.org, mingo@redhat.com,
acme@kernel.org, alexander.shishkin@linux.intel.com,
sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf: Fix CONFIG_KPROBE_EVENTS and CONFIG_UPROBE_EVENTS typos
Date: Thu, 16 Feb 2017 16:59:54 +1100 [thread overview]
Message-ID: <20170216165954.7cdc23e3@kryten> (raw)
In-Reply-To: <20170213065152.GA30715@gmail.com>
Hi Ingo,
> So the names should be fixed, it should be CONFIG_UPROBE_EVENTS and
> CONFIG_KPROBE_EVENTS throughout the code. It's CONFIG_PERF_EVENTS and
> CONFIG_PROBE_EVENTS after all and lives in kernel/events/ - all
> plural.
>
> I didn't notice the misnomer when merging these bits.
Ok, patch to follow.
Anton
prev parent reply other threads:[~2017-02-16 6:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-12 21:14 [PATCH] perf: Fix CONFIG_KPROBE_EVENTS and CONFIG_UPROBE_EVENTS typos Anton Blanchard
2017-02-13 2:49 ` David Miller
2017-02-13 6:51 ` Ingo Molnar
2017-02-16 5:59 ` Anton Blanchard [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=20170216165954.7cdc23e3@kryten \
--to=anton@samba.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sparclinux@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox