From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id E5EDE1C860C for ; Wed, 25 Feb 2026 07:48:20 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772005701; cv=none; b=UrfB+pHaAJ+fNJjS4sB3qGO2+0HiDXXSyZDLRWaHQwOoop3Z5oYgcHv8bEFzB0nhzH5jpj0/0zPvBjuBM04n3VK+r1TFgVUyJdXORkvEqYD+84ZvbWQhVqTIpjnvGp/F7Xwv8wCVyRdYnosRI3BeW1+sbQC4q9wbFJmkSbDQHHg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772005701; c=relaxed/simple; bh=mOZbZ1ZqqE+eiu5h8/XxBvggL38kFHopNnfib2JdFRk=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Wyxwi21sez+9TEEm8n8zmTNq1Tgq7NGcdSfU7ws+FQLG42f9epQlfeuYptpPdiRAHrSqSdUOdX6alQ3NhIhM4HBErbu/CnciEKvnW6xwOz1J8DltsOu2j98uQ5hBbU/7J3XoKHqq5BRqgzWMMsR8C2w2/BE/IkHjKDnUuKGcbCE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=H2YCJK4U; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="H2YCJK4U" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 170C3C116D0; Wed, 25 Feb 2026 07:48:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1772005700; bh=mOZbZ1ZqqE+eiu5h8/XxBvggL38kFHopNnfib2JdFRk=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=H2YCJK4UUb2ecASZN/fhJ0zl6u+XmlAuBCkCUGFOOKXxrgpE1+9Z9n8fs0r5/DDTA Ve/426cjDO9S6b6DXTf4xedXh2d+mY2wzmTZ68Ryre+E96FKxo84JlB+dEjfrM1qLN DYdYYzqTAJrhxsONSCxxGFxUNi5ySzJze87rDm3lqCpsaAfPou2bGD9pVZt7dEiElt D8Hv7CmP2sMQx+aENu1iKkUqqrgeil+xFea6ZTiQ1VIlke0b8xc6B9JD319kPgZh09 kXc1ry3fQtFo1CkBsS1ufSO8KUvp1rWRzXhq/oENVJCbrtKC85GiClzDeVRppEFCoh K9bqmtNXDr2lA== Date: Wed, 25 Feb 2026 13:18:16 +0530 From: Vinod Koul To: Siddharth Vadapalli Cc: nm@ti.com, vigneshr@ti.com, u-kumar1@ti.com, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, srk@ti.com Subject: Re: [PATCH v2] soc: ti: k3-ringacc: include platform_device header Message-ID: References: <20260220070242.470060-1-s-vadapalli@ti.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260220070242.470060-1-s-vadapalli@ti.com> On 20-02-26, 12:32, Siddharth Vadapalli wrote: > Users of "k3-ringacc" APIs may not necessarily be platform devices. Such > users therefore will not include "platform_device.h", resulting in > compilation warnings for the APIs declared in "k3-ringacc.h" which assume > inclusion of "platform_device.h" by its users. > > Fix the compilation warnings by including the "platform_device" header > file, which should ideally have been included since commit under Fixes. Which tree is this intended to get picked by? -- ~Vinod