From: Sasha Levin <sashal@kernel.org>
To: kernelci-results@groups.io
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, KernelCI bot <bot@kernelci.org>
Subject: Re: [REGRESSION] stable-rc/linux-6.1.y: (build)too few arguments to function ‘pm_runtime_get_if_active’; expected ...
Date: Thu, 19 Nov 2026 11:08:17 -0500 [thread overview]
Message-ID: <2026-11-19-1-daily-reply-0015@kernel.org> (raw)
In-Reply-To: <179500675212.301701.8262514497119491246@kernelci.org>
> too few arguments to function ‘pm_runtime_get_if_active’; expected 2, have 1 in drivers/dma/ste_dma40.o (drivers/dma/ste_dma40.c)
Thanks. This comes from the queued ste_dma40 series, not from a release. I'm
dropping 12787e3f2f93 ("dmaengine: ste_dma40: Check runtime PM in IRQ") and
c96e9f056095 ("dmaengine: ste_dma40: Validate disabled channel indexes") from
the 6.1, 5.15 and 5.10 queues: those trees take two arguments in
pm_runtime_get_if_active() and return a pointer from d40_hw_detect_init().
--
Thanks,
Sasha
prev parent reply other threads:[~2026-11-19 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 12:59 [REGRESSION] stable-rc/linux-6.1.y: (build)too few arguments to function ‘pm_runtime_get_if_active’; expected KernelCI bot
2026-11-19 16:08 ` 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=2026-11-19-1-daily-reply-0015@kernel.org \
--to=sashal@kernel.org \
--cc=bot@kernelci.org \
--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