OpenSBI Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 08:57:04 -0600	[thread overview]
Message-ID: <20261025145704.2570129-1-sebasjosue84@gmail.com> (raw)
In-Reply-To: <20261012022033.1165060-1-sebasjosue84@gmail.com>

Hi Anup,

Thanks for applying this.

One thing that belongs on the record: liutong sent the same fix a month
before mine, on 2026-09-10, as part of a v3 series.

  https://lore.kernel.org/r/20260910052629.3359493-4-liutong@iscas.ac.cn

Same function, same early exit, same Fixes tag. I was not aware of it
when I sent mine. It arrived as patch 3/4 of a series whose cover letter
is about integer overflows, and I had only checked the standalone July
patch for that function.

liutong is Cc'd here. That patch is still unmerged, so if you would
rather add a Reported-by or handle the credit some other way, that is
the right outcome as far as I am concerned.

Thanks,
Sebastian

-- 
opensbi mailing list
opensbi@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/opensbi

  parent reply	other threads:[~2026-10-25 14:57 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 [this message]
2026-10-26  3:38   ` Anup Patel
2026-10-26  3:50     ` Sebastian Alba Vives

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=20261025145704.2570129-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