public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kalle Valo <kvalo@kernel.org>, Jeff Johnson <jjohnson@kernel.org>
Cc: Balamurugan S <quic_bselvara@quicinc.com>,
	Jeff Johnson <jeff.johnson@oss.qualcomm.com>,
	P Praneesh <quic_ppranees@quicinc.com>,
	Raj Kumar Bhagat <quic_rajkbhag@quicinc.com>,
	Ath10k List <ath10k@lists.infradead.org>,
	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 ath-next tree
Date: Tue, 8 Apr 2025 10:51:46 +1000	[thread overview]
Message-ID: <20250408105146.459dfcf5@canb.auug.org.au> (raw)

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

Hi all,

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

drivers/net/wireless/ath/ath12k/ahb.c: In function 'ath12k_ahb_stop':
drivers/net/wireless/ath/ath12k/ahb.c:337:9: error: implicit declaration of function 'del_timer_sync'; did you mean 'dev_mc_sync'? [-Wimplicit-function-declaration]
  337 |         del_timer_sync(&ab->rx_replenish_retry);
      |         ^~~~~~~~~~~~~~
      |         dev_mc_sync

Caused by commit

  6cee30f0da75 ("wifi: ath12k: add AHB driver support for IPQ5332")

I have used the ath-next tree from next-20250407 for today.

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2025-04-08  0:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08  0:51 Stephen Rothwell [this message]
2025-04-08  1:06 ` linux-next: build failure after merge of the ath-next tree Dr. David Alan Gilbert
2025-04-08  1:37   ` Stephen Rothwell
2025-04-08 15:09     ` Jeff Johnson
2025-04-08 15:23       ` Jeff Johnson
2025-04-08 16:17         ` Jeff Johnson
2025-04-08 22:46           ` Stephen Rothwell

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=20250408105146.459dfcf5@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=ath10k@lists.infradead.org \
    --cc=jeff.johnson@oss.qualcomm.com \
    --cc=jjohnson@kernel.org \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=quic_bselvara@quicinc.com \
    --cc=quic_ppranees@quicinc.com \
    --cc=quic_rajkbhag@quicinc.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