sashing-ci | linux-clk

20261118-perso-ma35d1-upstream-clk-v11-0-bd1d1e060926@bootlin.com

✘ apply-series

'apply-series ../commits ...' (failure) · raw

apply-series ../commits 20261118-perso-ma35d1-upstream-clk-v11-0-bd1d1e060926@bootlin.com
 in dir /home/sashing/series/build (timeout 1200 secs)
 watching logfiles {}
 argv: [b'apply-series', b'../commits', b'20261118-perso-ma35d1-upstream-clk-v11-0-bd1d1e060926@bootlin.com']
 environment:
  BUILDBOT_BASEDIR=/home/sashing
  BUILDMASTER=localhost
  DEBIAN_FRONTEND=noninteractive
  HOME=/home/sashing
  HOSTNAME=sashing
  LC_CTYPE=C.UTF-8
  PATH=/opt/sashing/tasks:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/venv/bin
  PWD=/home/sashing/series/build
  WORKERNAME=local1
  container=podman
 using PTY: False
Single-message mode, ignoring any follow-ups
Looking up 20261118-perso-ma35d1-upstream-clk-v11-0-bd1d1e060926@bootlin.com
1 messages in the thread
---
Revision of 20261118-perso-ma35d1-upstream-clk-v11-0-bd1d1e060926@bootlin.com: v11
Looking up 20261118-perso-ma35d1-upstream-clk-v11-0-bd1d1e060926@bootlin.com
Checking for newer revisions
Grabbing search results from lore.kernel.org
Analyzing 11 messages in the thread
Looking for additional code-review trailers on lore.kernel.org
Analyzing 64 code-review messages
Checking attestation on all messages, may take a moment...
---
  v [PATCH v11 1/10] dt-bindings: clock: ma35d1: Mark HXT and LXT legacy
    + Message-ID: <20261118-perso-ma35d1-upstream-clk-v11-1-bd1d1e060926@bootlin.com>
  v [PATCH v11 2/10] clk: nuvoton: ma35d1: Use clk_hw pointers as mux parents
    + Message-ID: <20261118-perso-ma35d1-upstream-clk-v11-2-bd1d1e060926@bootlin.com>
  v [PATCH v11 3/10] clk: nuvoton: ma35d1: Avoid possible error pointer dereferencing
    + Message-ID: <20261118-perso-ma35d1-upstream-clk-v11-3-bd1d1e060926@bootlin.com>
  v [PATCH v11 4/10] clk: nuvoton: ma35d1: Retrieve HXT/LXT from DT when possible
    + Message-ID: <20261118-perso-ma35d1-upstream-clk-v11-4-bd1d1e060926@bootlin.com>
  v [PATCH v11 5/10] clk: nuvoton: ma35d1: Reparent the gates correctly
    + Message-ID: <20261118-perso-ma35d1-upstream-clk-v11-5-bd1d1e060926@bootlin.com>
  v [PATCH v11 6/10] clk: nuvoton: ma35d1: Use device managed helpers for fixed rate clocks
    + Message-ID: <20261118-perso-ma35d1-upstream-clk-v11-6-bd1d1e060926@bootlin.com>
  v [PATCH v11 7/10] clk: Create devm_clk_hw_register_fixed_rate_parent_hw()
    + Message-ID: <20261118-perso-ma35d1-upstream-clk-v11-7-bd1d1e060926@bootlin.com>
  v [PATCH v11 8/10] clk: nuvoton: ma35d1: Reparent SYSPLL correctly
    + Message-ID: <20261118-perso-ma35d1-upstream-clk-v11-8-bd1d1e060926@bootlin.com>
  v [PATCH v11 9/10] clk: nuvoton: ma35d1: Fix CCAP muxes bus width
    + Message-ID: <20261118-perso-ma35d1-upstream-clk-v11-9-bd1d1e060926@bootlin.com>
  v [PATCH v11 10/10] MAINTAINERS: Add myself as Nuvoton MA35D1 clock controller
    + Message-ID: <20261118-perso-ma35d1-upstream-clk-v11-10-bd1d1e060926@bootlin.com>
  ---
  v Signed: DKIM/bootlin.com
---
Total patches: 10
---
Applying: dt-bindings: clock: ma35d1: Mark HXT and LXT legacy
Applying: clk: nuvoton: ma35d1: Use clk_hw pointers as mux parents
Applying: clk: nuvoton: ma35d1: Avoid possible error pointer dereferencing
Patch failed at 0003 clk: nuvoton: ma35d1: Avoid possible error pointer dereferencing
error: patch failed: drivers/clk/nuvoton/clk-ma35d1-divider.c:90
error: drivers/clk/nuvoton/clk-ma35d1-divider.c: patch does not apply
error: patch failed: drivers/clk/nuvoton/clk-ma35d1-pll.c:336
error: drivers/clk/nuvoton/clk-ma35d1-pll.c: patch does not apply
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
program finished with exit code 128
elapsedTime=0.784942