From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 52D95FB5E8B for ; Tue, 17 Mar 2026 00:23:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:Content-Transfer-Encoding: Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To: From:Date:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=8EVtBK/g5VQELAXjopV7aXjZgUuOCBAWlo1q9i63uFI=; b=HHPFIsWQn/8HP0qDX2L4pozrL4 GyilHLPmAwgvTYT4At1t9IF1YmrMUdcJahTIYUdaSajhrQESBmFgYzhWkhIdq9sXFupHzzXQoNDK2 PHahXR++NZvuHKQjtLMUW0wLlNFu7zQ4K7WkLkrAfZS/twotpOTp6TpW+e8Ocume2dtREqXhW9cvY h3T0vOIulx9NYkEo6J+dMUpiz8aGahw+VoBAY8fGgkq2do1xLKw/UcKXUPt7UBEX5sQof8XToBkem UH4SRVbDZJkxl/QdPahtjE/aSQwOYSeR9aKZdNxKnrygWo0ctgKLPM+mfJpOMpSc/XAjhVkcrCK85 ITYvQNuQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98.2 #2 (Red Hat Linux)) id 1w2ID3-0000000581X-46xb; Tue, 17 Mar 2026 00:22:57 +0000 Received: from sea.source.kernel.org ([172.234.252.31]) by bombadil.infradead.org with esmtps (Exim 4.98.2 #2 (Red Hat Linux)) id 1w2ID1-0000000580u-19CN; Tue, 17 Mar 2026 00:22:56 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by sea.source.kernel.org (Postfix) with ESMTP id 733A443F78; Tue, 17 Mar 2026 00:22:53 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 306E3C19421; Tue, 17 Mar 2026 00:22:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1773706973; bh=CMU0rXMHkg7Kxz8EUxJAiLNslnr9+tAGsBMf/5Uzwgg=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=NEwjg4u7enwkX5/tJVpV1sCJowHXevufzg/wpiqivQYHvlPfWhwV9MAP9VJ1o5oy9 TZ2/BCnT8T/6UmejZz7sqvm5pguvIPTdIRgudemMoHRs/cgh/edkt76ZpwucNxSRgR X1wKb6i9gFMYrwf1RYPKD4jJyNPfgJzkjVg5pzVEf8kKmywet4kVGOtNTMHtTb9jpm jpwaL87DlLkvWOBnIv1w2O1iVkIcTLi6Cs+Y9VxMJZicevHuU1Ibo2U6+uEKBIubcb O2Puc6suuyZXZ87nmcHaNUJ7gspDgHzlAuw3LI8uOLT7STQWxFZOrhTAbrQJQEY+oy gxT9go35MvrhA== Date: Mon, 16 Mar 2026 17:22:51 -0700 From: Jakub Kicinski To: Daniel Lezcano Cc: konradybcio@kernel.org, andersson@kernel.org, linux-kernel@vger.kernel.org, Alex Elder , Andrew Lunn , "David S. Miller" , Eric Dumazet , Paolo Abeni , Jeff Johnson , Mathieu Poirier , Srinivas Kandagatla , Jaroslav Kysela , Takashi Iwai , Kees Cook , Greg Kroah-Hartman , Arnd Bergmann , Mark Brown , Wesley Cheng , netdev@vger.kernel.org, linux-wireless@vger.kernel.org, ath10k@lists.infradead.org, ath11k@lists.infradead.org, ath12k@lists.infradead.org, linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org, linux-sound@vger.kernel.org Subject: Re: [PATCH v2 0/4] Use the QMI service IDs from the QMI header Message-ID: <20260316172251.2d57d0aa@kernel.org> In-Reply-To: <20260316171419.2619620-1-daniel.lezcano@oss.qualcomm.com> References: <20260316171419.2619620-1-daniel.lezcano@oss.qualcomm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20260316_172255_363799_924A31A1 X-CRM114-Status: UNSURE ( 9.75 ) X-CRM114-Notice: Please train this message. X-BeenThere: ath10k@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "ath10k" Errors-To: ath10k-bounces+ath10k=archiver.kernel.org@lists.infradead.org On Mon, 16 Mar 2026 18:14:10 +0100 Daniel Lezcano wrote: > This series is based on the immutable branch [1] containing the QMI > service id definitions along with some drivers using them. > > How a patch can be merged ? Wait for the dependency to appear in respective trees after the merge window then repost the patches individually. I'm starting to get annoyed with all this cross-tree QMI/MHI noise.