From: Manuel Ebner <manuelebner@mailbox.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
corbet@lwn.net, skhan@linuxfoundation.org,
rdunlap@infradead.org, workflows@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Doc: process: Getting rid of OProfile url enlisting
Date: Sun, 16 Aug 2026 10:24:27 +0200 [thread overview]
Message-ID: <875527abdf9df0393ade872c6df3612ae9945b44.camel@mailbox.org> (raw)
In-Reply-To: <20260815220029.3711742-1-unixbhaskar@gmail.com>
On Sun, 2026-08-16 at 03:23 +0530, Bhaskar Chowdhury wrote:
> Aren't we done with this damn tool from a kernel perspective?? Thought,the link
> could be removed.
This would finalize (fix?) this commit 8e9fa2f21151 (oprofiled version
output line removed from the list)
Maybe add some reasoning (To reduce it's OS jitter or because it's a leftover link)
And if it's the way to handle translations remove:
Documentation/translations/it_IT/process/changes.rst:- <https://oprofile.sf.net/download/>
Documentation/translations/pt_BR/process/changes.rst:- <https://oprofile.sf.net/download/>
I have no clue about the technical side, that's why I'm asking:
Can this be removed aswell?
arch/sparc/kernel/nmi.c:atomic_t nmi_active = ATOMIC_INIT(0); /* oprofile uses this */
Thanks
Manuel
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
> ---
> Documentation/process/changes.rst | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/Documentation/process/changes.rst b/Documentation/process/changes.rst
> index 0aa232b117b5..336c07190c9b 100644
> --- a/Documentation/process/changes.rst
> +++ b/Documentation/process/changes.rst
> @@ -556,10 +556,6 @@ Ip-route2
>
> - <https://www.kernel.org/pub/linux/utils/net/iproute2/>
>
> -OProfile
> ---------
> -
> -- <https://oprofile.sf.net/download/>
>
> Kernel documentation
> ********************
> --
> 2.54.0
>
next prev parent reply other threads:[~2026-08-16 8:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-15 21:53 Bhaskar Chowdhury
2026-08-15 22:33 ` Matthew Wilcox
2026-08-16 8:24 ` Manuel Ebner [this message]
2026-08-16 15:07 ` Randy Dunlap
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=875527abdf9df0393ade872c6df3612ae9945b44.camel@mailbox.org \
--to=manuelebner@mailbox.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=unixbhaskar@gmail.com \
--cc=workflows@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
all inboxes | Powered by JetHome®