From: Mark Brown <broonie@kernel.org>
To: Frank Li <Frank.li@nxp.com>
Cc: Jaidev Shastri <jaidevshastri@vt.edu>,
Kees Cook <kees@kernel.org>, Kees Cook <kees+treewide@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: manual merge of the imx-mxs tree with the origin tree
Date: Mon, 9 Nov 2026 13:30:31 +0000 [thread overview]
Message-ID: <avHK9yttDdx1O5P8@sirena.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1497 bytes --]
Hi all,
Today's linux-next merge of the imx-mxs tree got a conflict in:
drivers/firmware/imx/imx-scu-irq.c
between commit:
4dd10fbbeb9c3 ("treewide: Convert devm_kmalloc() family to the devm_kmalloc_obj() family")
from the origin tree and commit:
f144d9f031b01 ("firmware: imx: scu: publish the SCU IPC handles with release semantics")
from the imx-mxs tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
diff --cc drivers/firmware/imx/imx-scu-irq.c
index bc22b10ddb20f,4f24e3c08a652..0000000000000
--- a/drivers/firmware/imx/imx-scu-irq.c
+++ b/drivers/firmware/imx/imx-scu-irq.c
@@@ -219,7 -223,15 +223,15 @@@ int imx_scu_enable_general_irq_channel(
if (ret)
return ret;
+ /*
+ * imx_scu_irq_group_enable() tests imx_sc_irq_ipc_handle from other
+ * drivers' probe paths and then passes it to imx_scu_call_rpc().
+ * Publish it with release semantics so that the SCU state it points
+ * to is visible to them.
+ */
+ smp_store_release(&imx_sc_irq_ipc_handle, ipc);
+
- cl = devm_kzalloc(dev, sizeof(*cl), GFP_KERNEL);
+ cl = devm_kzalloc_obj(dev, *cl);
if (!cl)
return -ENOMEM;
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
reply other threads:[~2026-11-09 13:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=avHK9yttDdx1O5P8@sirena.co.uk \
--to=broonie@kernel.org \
--cc=Frank.li@nxp.com \
--cc=jaidevshastri@vt.edu \
--cc=kees+treewide@kernel.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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
all inboxes | Powered by JetHome®