Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: cki-project@redhat.com
Cc: catalin.marinas@arm.com, linux-arm-kernel@lists.infradead.org,
	steve.price@arm.com
Subject: Re: ❌ FAIL: Test report for for-kernelci (6.14.0-rc2, upstream-arm-next, a64dcfb4)
Date: Thu, 13 Feb 2025 15:42:38 +0000	[thread overview]
Message-ID: <20250213154237.GA11897@willie-the-truck> (raw)
In-Reply-To: <64234.125021309531800883@us-mta-201.us.mimecast.lan>

[+Steven]

On Thu, Feb 13, 2025 at 02:53:16PM -0000, cki-project@redhat.com wrote:
> Hi, we tested your kernel and here are the results:
> 
>     Overall result: FAILED
>              Merge: OK
>            Compile: FAILED
> 
> 
> Kernel information:
>     Commit message: Linux 6.14-rc2
> 
> You can find all the details about the test run at
>     https://datawarehouse.cki-project.org/kcidb/checkouts/redhat:1669747201
> 
> One or more kernel builds failed:
>     Unrecognized or new issues:
>          aarch64 - https://datawarehouse.cki-project.org/kcidb/builds/redhat:1669747201-aarch64-kernel

00:14:01 drivers/gpu/drm/panthor/panthor_fw.c: In function ‘panthor_fw_read_build_info’:
00:14:01 drivers/gpu/drm/panthor/panthor_fw.c:641:53: error: initializer-string for array of ‘char’ is too long [-Werror=unterminated-string-initialization]
00:14:01   641 |         const char git_sha_header[sizeof(header)] = "git_sha: ";
00:14:01       |                                                     ^~~~~~~~~~~

Will


      reply	other threads:[~2025-02-13 16:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-13 14:53 ❌ FAIL: Test report for for-kernelci (6.14.0-rc2, upstream-arm-next, a64dcfb4) cki-project
2025-02-13 15:42 ` Will Deacon [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=20250213154237.GA11897@willie-the-truck \
    --to=will@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=cki-project@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=steve.price@arm.com \
    /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