All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: linaro-toolchain@lists.linaro.org
Cc: llvm@lists.linux.dev
Subject: Re: [Linaro-TCWG-CI] v6.18-rc1-73-g3ffeb17a9a27a: Failure on aarch64
Date: Mon, 17 Nov 2025 09:24:57 -0700	[thread overview]
Message-ID: <20251117162457.GA564441@ax162> (raw)
In-Reply-To: <1094974019.2375.1763286384876@jenkins.jenkins>

On Sun, Nov 16, 2025 at 09:46:23AM +0000, ci_notify@linaro.org wrote:
> Dear contributor,
> 
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
> 
> In tcwg_kernel/llvm-master-aarch64-next-allmodconfig, after:
>   | commit v6.18-rc1-73-g3ffeb17a9a27a
>   | Author: Christian Marangi <ansuelsmth@gmail.com>
>   | Date:   Fri Nov 7 00:57:08 2025 +0100
>   | 
>   |     pinctrl: airoha: add support for Airoha AN7583 PINs
>   |     
>   |     Add all the required entry to add suppot for Airoha AN7583 PINs.
>   |     
>   |     Where possible the same function group are used from Airoha EN7581 to
>   | ... 4 lines of the commit log omitted.
> 
> Produces Failure:
>   | Results changed to
>   | # reset_artifacts:
>   | -10
>   | # build_abe binutils:
>   | -9
>   | # build_kernel_llvm:
>   | -5
>   | # build_abe qemu:
>   | -2
>   | # linux_n_obj:
>   | 27020
>   | # First few build errors in logs:
>   | # 00:37:42 drivers/pinctrl/mediatek/pinctrl-airoha.c:2064:41: error: variable 'an7583_pinctrl_drive_e2_conf' is not needed and will not be emitted [-Werror,-Wunneeded-internal-declaration]

https://lore.kernel.org/20251112-pinctrl-airoha-fix-an7583-drive-e2-confg-usage-v1-1-d2550d55e988@kernel.org/

Cheers,
Nathan

      reply	other threads:[~2025-11-17 16:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-16  9:46 [Linaro-TCWG-CI] v6.18-rc1-73-g3ffeb17a9a27a: Failure on aarch64 ci_notify
2025-11-17 16:24 ` Nathan Chancellor [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=20251117162457.GA564441@ax162 \
    --to=nathan@kernel.org \
    --cc=linaro-toolchain@lists.linaro.org \
    --cc=llvm@lists.linux.dev \
    /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.