From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
Cc: "Dr. David Alan Gilbert" <linux@treblig.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@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>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
"ath12k@lists.infradead.org" <ath12k@lists.infradead.org>
Subject: Re: linux-next: build failure after merge of the ath-next tree
Date: Wed, 9 Apr 2025 08:46:37 +1000 [thread overview]
Message-ID: <20250409084637.3bd593c6@canb.auug.org.au> (raw)
In-Reply-To: <4ae387b2-0dd7-413b-b66c-1f136455e23f@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 542 bytes --]
Hi Jeff,
On Tue, 8 Apr 2025 09:17:21 -0700 Jeff Johnson <jeff.johnson@oss.qualcomm.com> wrote:
>
> On 4/8/2025 8:23 AM, Jeff Johnson wrote:
> > NM. Since the timer_delete_sync() API is already in my tree I can make a
> > one-off patch for this.
>
> please review https://msgid.link/20250408-timer_delete_sync-v1-1-4dcb22f71083@oss.qualcomm.com
>
> I'll wait a bit for any tags to accumulate before I merge into ath-next
I'll use your patch in the ath-next tree merge today (if necessary).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2025-04-08 22:46 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
2025-04-08 15:23 ` Jeff Johnson
2025-04-08 16:17 ` Jeff Johnson
2025-04-08 22:46 ` Stephen Rothwell [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=20250409084637.3bd593c6@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=ath12k@lists.infradead.org \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=jjohnson@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=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