From: Ben Hutchings <benh@debian.org>
To: stable@vger.kernel.org
Cc: James Clark <james.clark@linaro.org>
Subject: [PATCH 5.4,4.10 1/2] perf cs-etm: Add missing variable in cs_etm__process_queues()
Date: Mon, 24 Feb 2025 16:57:20 +0100 [thread overview]
Message-ID: <Z7yW4FuPxoZyl7Ga@decadent.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
Commit 5afd032961e8 "perf cs-etm: Don't flush when packet_queue fills
up" uses i as a loop counter in cs_etm__process_queues(). It was
backported to the 5.4 and 5.10 stable branches, but the i variable
doesn't exist there as it was only added in 5.15.
Declare i with the expected type.
Fixes: 1ed167325c32 ("perf cs-etm: Don't flush when packet_queue fills up")
Fixes: 26db806fa23e ("perf cs-etm: Don't flush when packet_queue fills up")
Signed-off-by: Ben Hutchings <benh@debian.org>
---
tools/perf/util/cs-etm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/perf/util/cs-etm.c b/tools/perf/util/cs-etm.c
index e3fa32b83367..2055d582a8a4 100644
--- a/tools/perf/util/cs-etm.c
+++ b/tools/perf/util/cs-etm.c
@@ -2171,7 +2171,7 @@ static int cs_etm__process_timeless_queues(struct cs_etm_auxtrace *etm,
static int cs_etm__process_queues(struct cs_etm_auxtrace *etm)
{
int ret = 0;
- unsigned int cs_queue_nr, queue_nr;
+ unsigned int cs_queue_nr, queue_nr, i;
u8 trace_chan_id;
u64 timestamp;
struct auxtrace_queue *queue;
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2025-02-24 16:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 15:57 Ben Hutchings [this message]
2025-02-24 16:00 ` [PATCH 5.4,5.10 2/2] udf: Fix use of check_add_overflow() with mixed type arguments Ben Hutchings
2025-02-24 22:28 ` Ben Hutchings
2025-03-10 16:29 ` Greg KH
2025-03-11 17:00 ` Ben Hutchings
2025-03-13 15:42 ` Greg KH
2025-02-25 16:13 ` Sasha Levin
2025-02-25 16:13 ` [PATCH 5.4,4.10 1/2] perf cs-etm: Add missing variable in cs_etm__process_queues() Sasha Levin
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=Z7yW4FuPxoZyl7Ga@decadent.org.uk \
--to=benh@debian.org \
--cc=james.clark@linaro.org \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.