From: Heiko Carstens <hca@linux.ibm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Robert Richter <rric@kernel.org>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Arnd Bergmann <arnd@kernel.org>,
oprofile-list@lists.sf.net, William Cohen <wcohen@redhat.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
anmar.oueja@linaro.org, Christoph Hellwig <hch@infradead.org>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 12/18] arch: s390: Remove CONFIG_OPROFILE support
Date: Fri, 15 Jan 2021 11:35:29 +0100 [thread overview]
Message-ID: <20210115103529.GA10194@osiris> (raw)
In-Reply-To: <d898acaf9320125e9c23b18a16ecd88d70f24170.1610622251.git.viresh.kumar@linaro.org>
On Thu, Jan 14, 2021 at 05:05:25PM +0530, Viresh Kumar wrote:
> The "oprofile" user-space tools don't use the kernel OPROFILE support
> any more, and haven't in a long time. User-space has been converted to
> the perf interfaces.
>
> Remove the old oprofile's architecture specific support.
>
> Suggested-by: Christoph Hellwig <hch@infradead.org>
> Suggested-by: Linus Torvalds <torvalds@linux-foundation.org>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
> arch/s390/Kconfig | 1 -
> arch/s390/Makefile | 3 ---
> arch/s390/configs/debug_defconfig | 1 -
> arch/s390/configs/defconfig | 1 -
> arch/s390/oprofile/Makefile | 10 ---------
> arch/s390/oprofile/init.c | 37 -------------------------------
> 6 files changed, 53 deletions(-)
> delete mode 100644 arch/s390/oprofile/Makefile
> delete mode 100644 arch/s390/oprofile/init.c
Acked-by: Heiko Carstens <hca@linux.ibm.com>
prev parent reply other threads:[~2021-01-15 10:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1610622251.git.viresh.kumar@linaro.org>
2021-01-14 11:35 ` [PATCH 12/18] arch: s390: Remove CONFIG_OPROFILE support Viresh Kumar
2021-01-15 10:35 ` Heiko Carstens [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=20210115103529.GA10194@osiris \
--to=hca@linux.ibm.com \
--cc=anmar.oueja@linaro.org \
--cc=arnd@kernel.org \
--cc=borntraeger@de.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=oprofile-list@lists.sf.net \
--cc=rric@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=viro@zeniv.linux.org.uk \
--cc=wcohen@redhat.com \
/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