public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jassi Brar <jassisinghbrar@gmail•com>
Cc: Jason-JH Lin <jason-jh.lin@mediatek•com>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build failure after merge of the mailbox tree
Date: Tue, 27 May 2025 15:50:10 +1000	[thread overview]
Message-ID: <20250527155010.0ef7015f@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 698 bytes --]

Hi all,

After merging the mailbox tree, today's linux-next build (x86_64
allmodconfig) failed like this:

drivers/media/platform/mediatek/mdp3/mtk-mdp3-core.c: In function 'mdp_probe':
drivers/media/platform/mediatek/mdp3/mtk-mdp3-core.c:297:41: error: implicit declaration of function 'cmdq_get_shift_pa' [-Wimplicit-function-declaration]
  297 |                 mdp->cmdq_shift_pa[i] = cmdq_get_shift_pa(mdp->cmdq_clt[i]->chan);
      |                                         ^~~~~~~~~~~~~~~~~

Caused by commit

  1f808916c0a6 ("mailbox: mtk-cmdq: Remove unsued cmdq_get_shift_pa()")

I have used the mailbox tree from next-20250526 for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2025-05-27  5:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-27  5:50 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-12-10 23:49 linux-next: build failure after merge of the mailbox tree Stephen Rothwell
2025-12-11  0:01 ` Jassi Brar
2025-12-11 17:28   ` Jason-JH Lin (林睿祥)
2025-10-07 12:04 Mark Brown
2025-10-06 11:54 Mark Brown
2025-07-21  3:13 Stephen Rothwell
2023-08-31  1:00 Stephen Rothwell
2017-03-29  5:17 Stephen Rothwell
2015-11-01 12:12 Stephen Rothwell
2015-11-04  2:57 ` Jassi Brar
2015-11-04  8:16   ` Lee Jones

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=20250527155010.0ef7015f@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=jason-jh.lin@mediatek$(echo .)com \
    --cc=jassisinghbrar@gmail$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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