From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: irenic.rajneesh@gmail.com, david.e.box@linux.intel.com,
hdegoede@redhat.com, linux@treblig.org
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org,
platform-driver-x86@vger.kernel.org, hpa@zytor.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] platform/x86: intel_telemetry: Remove deadcode
Date: Mon, 09 Jun 2025 13:04:19 +0300 [thread overview]
Message-ID: <174946345966.3675.2007813244363355783.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20250608012512.377134-1-linux@treblig.org>
On Sun, 08 Jun 2025 02:25:09 +0100, linux@treblig.org wrote:
> Many of the entries in the Telemetry core driver are not called
> anywhere, and haven't been since they were originally added in 2016.
>
> Remove them.
>
> Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
>
> [...]
Thank you for your contribution, it has been applied to my local
review-ilpo-next branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-next branch only once I've pushed my
local branch there, which might take a while.
The list of commits applied:
[1/3] platform/x86: intel_telemetry: Remove unused telemetry_*_events
commit: 22428723a27e6ee03dffd86ba62501bffe5b4c78
[2/3] platform/x86: intel_telemetry: Remove unused [gs]et_sampling_period
commit: 2ad029bde3d4dd7787483f646384a93a95922cf8
[3/3] platform/x86: intel_telemetry: Remove unused telemetry_raw_read_events
commit: 458957b8e3d552701cdb55ffacc38627d2039fe8
--
i.
prev parent reply other threads:[~2025-06-09 10:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-08 1:25 linux
2025-06-08 1:25 ` [PATCH 1/3] platform/x86: intel_telemetry: Remove unused telemetry_*_events linux
2025-06-08 1:25 ` [PATCH 2/3] platform/x86: intel_telemetry: Remove unused [gs]et_sampling_period linux
2025-06-08 1:25 ` [PATCH 3/3] platform/x86: intel_telemetry: Remove unused telemetry_raw_read_events linux
2025-06-09 10:04 ` Ilpo Järvinen [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=174946345966.3675.2007813244363355783.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=david.e.box@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=hpa@zytor.com \
--cc=irenic.rajneesh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
--cc=mingo@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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®