public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: Krzysztof Kozlowski <krzk@kernel.org>,
	Alim Akhtar <alim.akhtar@samsung.com>
Cc: linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, peter.griffin@linaro.org,
	andre.draszik@linaro.org, jyescas@google.com,
	kernel-team@android.com, stable@vger.kernel.org
Subject: Re: [PATCH v3 0/6] firmware: samsung: acpm: Various fixes for sashiko bug reports
Date: Fri, 1 May 2026 13:23:04 +0300	[thread overview]
Message-ID: <380547be-8eda-4395-b13c-b6cb6804ec5b@linaro.org> (raw)
In-Reply-To: <20260429-acpm-fixes-sashiko-reports-v3-0-47cf74ab09ad@linaro.org>


FYI, sashiko identified few improvements for the current set.
I'm preparing v4.

Thanks!
ta


      parent reply	other threads:[~2026-05-01 10:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-29 13:11 [PATCH v3 0/6] firmware: samsung: acpm: Various fixes for sashiko bug reports Tudor Ambarus
2026-04-29 13:11 ` [PATCH v3 1/6] firmware: samsung: acpm: Fix cross-thread RX length corruption Tudor Ambarus
2026-04-29 13:11 ` [PATCH v3 2/6] firmware: samsung: acpm: Fix mailbox channel leak on probe error Tudor Ambarus
2026-04-29 13:11 ` [PATCH v3 3/6] firmware: samsung: acpm: Fix dummy stubs to return ERR_PTR Tudor Ambarus
2026-04-29 13:11 ` [PATCH v3 4/6] firmware: samsung: acpm: Validate SRAM shared memory and queue pointers Tudor Ambarus
2026-05-01 12:23   ` Tudor Ambarus
2026-04-29 13:11 ` [PATCH v3 5/6] firmware: samsung: acpm: Fix infinite loop on sequence number exhaustion Tudor Ambarus
2026-04-29 13:11 ` [PATCH v3 6/6] firmware: samsung: acpm: Fix memory ordering races in RX and polling paths Tudor Ambarus
2026-05-01 10:23 ` Tudor Ambarus [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=380547be-8eda-4395-b13c-b6cb6804ec5b@linaro.org \
    --to=tudor.ambarus@linaro.org \
    --cc=alim.akhtar@samsung.com \
    --cc=andre.draszik@linaro.org \
    --cc=jyescas@google.com \
    --cc=kernel-team@android.com \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=peter.griffin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox