From: Ranbir Singh <ranbir.singh@oss.qualcomm.com>
To: opensbi@lists.infradead.org
Cc: Rahul Pathak <rahul.pathak@oss.qualcomm.com>
Subject: [PATCH v2 2/2] lib: utils/mpxy: logging: Use correct enum for enable notification
Date: Fri, 24 Jul 2026 13:39:20 +0530 [thread overview]
Message-ID: <20260724080920.1629065-3-ranbir.singh@oss.qualcomm.com> (raw)
In-Reply-To: <20260724080920.1629065-1-ranbir.singh@oss.qualcomm.com>
Logging file should be using its own enum and not others.
Fixes: 262571217c75 ("lib: utils/mpxy: Add RPMI MPXY driver for logging
service group")
Signed-off-by: Ranbir Singh <ranbir.singh@oss.qualcomm.com>
Reviewed-by: Rahul Pathak <rahul.pathak@oss.qualcomm.com>
---
lib/utils/mpxy/fdt_mpxy_rpmi_logging.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/utils/mpxy/fdt_mpxy_rpmi_logging.c b/lib/utils/mpxy/fdt_mpxy_rpmi_logging.c
index e8f085eb..1e92053d 100644
--- a/lib/utils/mpxy/fdt_mpxy_rpmi_logging.c
+++ b/lib/utils/mpxy/fdt_mpxy_rpmi_logging.c
@@ -11,7 +11,7 @@
static struct mpxy_rpmi_service_data logging_services[] = {
[0] = {
- .id = RPMI_MM_SRV_ENABLE_NOTIFICATION,
+ .id = RPMI_LOGGING_SRV_ENABLE_NOTIFICATION,
.min_tx_len = sizeof(struct rpmi_enable_notification_req),
.max_tx_len = sizeof(struct rpmi_enable_notification_req),
.min_rx_len = sizeof(struct rpmi_enable_notification_resp),
--
2.43.0
--
opensbi mailing list
opensbi@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/opensbi
prev parent reply other threads:[~2026-07-24 8:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 8:09 [PATCH v2 0/2] Fix Enable Notification Ranbir Singh
2026-07-24 8:09 ` [PATCH v2 1/2] lib: utils/mpxy: mm: Add missing RPMI_MM_SRV_ENABLE_NOTIFICATION entry Ranbir Singh
2026-07-24 8:09 ` Ranbir Singh [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=20260724080920.1629065-3-ranbir.singh@oss.qualcomm.com \
--to=ranbir.singh@oss.qualcomm.com \
--cc=opensbi@lists.infradead.org \
--cc=rahul.pathak@oss.qualcomm.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