From: Sebastian Alba Vives <sebasjosue84@gmail.com>
To: opensbi@lists.infradead.org
Cc: anup.patel@oss.qualcomm.com, liutong@iscas.ac.cn,
david.garcia@aheadcomputing.com,
Sebastian Alba Vives <sebasjosue84@gmail.com>
Subject: Re: [PATCH] lib: sbi_pmu: unmap shared memory on the early exit in event_get_info
Date: Sun, 25 Oct 2026 21:50:13 -0600 [thread overview]
Message-ID: <20261026035013.2728338-1-sebasjosue84@gmail.com> (raw)
In-Reply-To: <CAAhSdy21+URDb3TWXjhzrQhXjzrvpg1SFta5F95AHrZFKR=3Lg@mail.gmail.com>
Hi Anup,
Makes sense, and I agree on not rewriting published commits.
Fair point on flagging it sooner, too. I spotted liutong's patch on
12 October and didn't say anything until after this one had landed, so
that part is on me. I'll raise duplicates the same day from now on.
Leaving the record in the thread is fine by me, nothing else needed
from my end.
Thanks,
Sebastian
--
opensbi mailing list
opensbi@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/opensbi
prev parent reply other threads:[~2026-10-26 3:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 2:20 [PATCH] lib: sbi_pmu: unmap shared memory on the early exit in event_get_info Sebastian Alba Vives
2026-10-25 8:36 ` Anup Patel
2026-10-25 14:57 ` Sebastian Alba Vives
2026-10-26 3:38 ` Anup Patel
2026-10-26 3:50 ` Sebastian Alba Vives [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=20261026035013.2728338-1-sebasjosue84@gmail.com \
--to=sebasjosue84@gmail.com \
--cc=anup.patel@oss.qualcomm.com \
--cc=david.garcia@aheadcomputing.com \
--cc=liutong@iscas.ac.cn \
--cc=opensbi@lists.infradead.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