Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: kernelci-results@groups.io
Cc: Sasha Levin <sashal@kernel.org>,
	gus@collabora.com, stable@vger.kernel.org,
	KernelCI bot <bot@kernelci.org>
Subject: Re: [REGRESSION] stable-rc/linux-6.12.y: (build) incompatible pointer types passing 'u32 (*)[4]' (aka 'unsigned int...
Date: Fri, 29 May 2026 08:44:04 -0400	[thread overview]
Message-ID: <20260529120000.armffa-rc-drop@kernel.org> (raw)
In-Reply-To: <178001274428.7152.372661732178917650@330cfa3079ca>

On Thu, May 28, 2026 at 11:59:04PM -0000, KernelCI bot wrote:
> /tmp/kci/linux/drivers/firmware/arm_ffa/driver.c:381:14: error: incompatible pointer types passing 'u32 (*)[4]' (aka 'unsigned int (*)[4]') to parameter of type 'uuid_t *' [-Werror,-Wincompatible-pointer-types]
>   381 |                         uuid_copy(&buf->uuid, &uuid_regs.uuid);

Thanks for the report. In 6.12 struct ffa_partition_info.uuid is still
'u32 uuid[4]', not uuid_t, so uuid_copy(&buf->uuid, ...) fails to
compile. The conversion prerequisite b7c9f32614f17 ("firmware: arm_ffa:
Replace UUID buffer to standard UUID format") isn't in 6.12. Dropped the
offending patch from the 6.12 queue along with its dependency:
  - "firmware: arm_ffa: fix big-endian support in __ffa_partition_info_get_regs"

--
Thanks,
Sasha

      reply	other threads:[~2026-05-29 12:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-28 23:59 [REGRESSION] stable-rc/linux-6.12.y: (build) incompatible pointer types passing 'u32 (*)[4]' (aka 'unsigned int KernelCI bot
2026-05-29 12:44 ` Sasha Levin [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=20260529120000.armffa-rc-drop@kernel.org \
    --to=sashal@kernel.org \
    --cc=bot@kernelci.org \
    --cc=gus@collabora.com \
    --cc=kernelci-results@groups.io \
    --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