From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
"Dr. David Alan Gilbert" <linux@treblig.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>
Cc: Kalle Valo <kvalo@kernel.org>, Jeff Johnson <jjohnson@kernel.org>,
Balamurugan S <quic_bselvara@quicinc.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: Re: linux-next: build failure after merge of the ath-next tree
Date: Tue, 8 Apr 2025 08:09:05 -0700 [thread overview]
Message-ID: <26cafcbb-6a94-40ab-aabf-3c9943cfb925@oss.qualcomm.com> (raw)
In-Reply-To: <20250408113747.3a10275a@canb.auug.org.au>
On 4/7/2025 6:37 PM, Stephen Rothwell wrote:
> Hi Dave,
>
> On Tue, 8 Apr 2025 01:06:28 +0000 "Dr. David Alan Gilbert" <linux@treblig.org> wrote:
>>
>> * Stephen Rothwell (sfr@canb.auug.org.au) wrote:
>>>
>>> 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.
>>
>> I guess a clash with the recent:
>> Fixes: 8fa7292fee5c ("treewide: Switch/rename to timer_delete[_sync]()")
>
> I will try that out tomorrow.
Yes, looks like you'll need to carry a patch:
s/del_timer_sync/timer_delete_sync/
Until that renaming patch makes it down to my tree and we rename.
next prev parent reply other threads:[~2025-04-08 15:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 0:51 linux-next: build failure after merge of the ath-next tree Stephen Rothwell
2025-04-08 1:06 ` Dr. David Alan Gilbert
2025-04-08 1:37 ` Stephen Rothwell
2025-04-08 15:09 ` Jeff Johnson [this message]
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=26cafcbb-6a94-40ab-aabf-3c9943cfb925@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@treblig.org \
--cc=mingo@kernel.org \
--cc=quic_bselvara@quicinc.com \
--cc=quic_ppranees@quicinc.com \
--cc=quic_rajkbhag@quicinc.com \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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