From: Thomas Gleixner <tglx@kernel.org>
To: Douglas Anderson <dianders@chromium.org>, jassisinghbrar@gmail.com
Cc: Douglas Anderson <dianders@chromium.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 06/15] irqchip/qcom-mpm: Use mbox_ring_doorbell() instead of NULL message
Date: Tue, 17 Feb 2026 11:11:06 +0100 [thread overview]
Message-ID: <87v7fvel39.ffs@tglx> (raw)
In-Reply-To: <20260216100943.v3.6.I59d887fd641f70e40950b7545ed31f193cd1c270@changeid>
On Mon, Feb 16 2026 at 10:09, Douglas Anderson wrote:
> As per the patch ("mailbox: Deprecate NULL mbox messages; Introduce
> mbox_ring_doorbell()"), we want to switch all users of NULL mailbox
> messages to use mbox_ring_doorbell().
>
> This client only ever sent NULL messages, so the transition is
> straightforward.
>
> This client didn't previously call mbox_client_txdone() and it appears
> that the mailboxes it hooks up with (qcom-apcs-ipc-mailbox.c or
> qcom-ipcc.c) have both `txdone_irq` and `txdone_poll` as
> false. Presumably this means the client was relying the mailbox core's
> quirky behavior when sending NULL messages.
>
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
Acked-by: Thomas Gleixner <tglx@kernel.org>
next prev parent reply other threads:[~2026-02-17 10:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 18:09 [PATCH v3 00/15] mailbox: Stop sending NULL mailbox messages Douglas Anderson
2026-02-16 18:09 ` [PATCH v3 01/15] mailbox: Deprecate NULL mbox messages; Introduce mbox_ring_doorbell() Douglas Anderson
2026-03-10 3:23 ` Jassi Brar
2026-03-10 15:08 ` Doug Anderson
2026-02-16 18:09 ` [PATCH v3 02/15] ACPI: PCC: Use mbox_ring_doorbell() instead of NULL message Douglas Anderson
2026-02-16 18:09 ` [PATCH v3 03/15] firmware: arm_scmi: " Douglas Anderson
2026-02-16 18:09 ` [PATCH v3 04/15] firmware: imx-dsp: " Douglas Anderson
2026-02-16 18:09 ` [PATCH v3 05/15] firmware: tegra: bpmp: " Douglas Anderson
2026-02-16 18:09 ` [PATCH v3 06/15] irqchip/qcom-mpm: " Douglas Anderson
2026-02-17 10:11 ` Thomas Gleixner [this message]
2026-02-16 18:09 ` [PATCH v3 07/15] remoteproc: xlnx: " Douglas Anderson
2026-02-16 18:09 ` [PATCH v3 08/15] rpmsg: qcom_glink_rpm: " Douglas Anderson
2026-02-16 18:09 ` [PATCH v3 09/15] rpmsg: glink: smem: " Douglas Anderson
2026-02-16 18:09 ` [PATCH v3 10/15] rpmsg: qcom_smd: " Douglas Anderson
2026-02-16 18:09 ` [PATCH v3 11/15] soc: qcom: aoss: " Douglas Anderson
2026-02-23 15:45 ` Bjorn Andersson
2026-02-16 18:09 ` [PATCH v3 12/15] soc: qcom: smp2p: " Douglas Anderson
2026-02-23 15:46 ` Bjorn Andersson
2026-02-16 18:09 ` [PATCH v3 13/15] soc: qcom: smsm: " Douglas Anderson
2026-02-23 15:46 ` Bjorn Andersson
2026-02-16 18:09 ` [PATCH v3 14/15] soc: ti: wkup_m3_ipc: " Douglas Anderson
2026-02-16 18:09 ` [PATCH v3 15/15] drivers: firmware: xilinx: " Douglas Anderson
2026-03-09 15:19 ` [PATCH v3 00/15] mailbox: Stop sending NULL mailbox messages Doug Anderson
2026-03-11 0:16 ` Doug Anderson
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=87v7fvel39.ffs@tglx \
--to=tglx@kernel.org \
--cc=dianders@chromium.org \
--cc=jassisinghbrar@gmail.com \
--cc=linux-kernel@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.