The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Siddharth Vadapalli <s-vadapalli@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: <s-vadapalli@ti.com>, Vinod Koul <vkoul@kernel.org>,
	<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
Date: Wed, 25 Feb 2026 16:08:45 +0530	[thread overview]
Message-ID: <3e005688-e479-4109-86b1-c2490cee1a8f@ti.com> (raw)
In-Reply-To: <20260225102839.652wkz4o2fxe5eok@jimmy>

On 25/02/26 15:58, Nishanth Menon wrote:
> On 15:33-20260225, Siddharth Vadapalli wrote:
>> On 25/02/26 13:18, Vinod Koul wrote:
>>> 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?
>>>
>>
>> I assume it is the SoC tree since 'get_maintainer.pl' doesn't output a
>> mailing list apart from 'linux-kernel@vger.kernel.org'.
>>
> 
> drivers/soc/ti/k3-ringacc.c already includes the header.. so who needs
> it?
> 

At the point in time that the v1 patch was posted, this was needed for the 
patch in an RFC series:
https://lore.kernel.org/r/20240518124234.2671651-19-s-vadapalli@ti.com/
Although the RFC series hasn't been merged, since it is still possible for
non platform-device users to call the DMA APIs which in turn depend on the 
k3-ringacc APIs being exported, I posted the v2 patch.

If you believe that this patch should be posted along with the dependent 
series, I will do so and the patch can be ignored.

Regards,
Siddharth.

  reply	other threads:[~2026-02-25 10:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-20  7:02 [PATCH v2] soc: ti: k3-ringacc: include platform_device header Siddharth Vadapalli
2026-02-25  7:48 ` Vinod Koul
2026-02-25 10:03   ` Siddharth Vadapalli
2026-02-25 10:28     ` Nishanth Menon
2026-02-25 10:38       ` Siddharth Vadapalli [this message]
2026-02-25 11:57         ` Nishanth Menon

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=3e005688-e479-4109-86b1-c2490cee1a8f@ti.com \
    --to=s-vadapalli@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=srk@ti.com \
    --cc=u-kumar1@ti.com \
    --cc=vigneshr@ti.com \
    --cc=vkoul@kernel.org \
    /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