From: Frank Rowand <frowand.list@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>,
Rob Herring <robh+dt@kernel.org>
Cc: Lorenzo Pieralisi <lpieralisi@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] of/device: Fix up of_dma_configure_id() stub
Date: Thu, 25 Aug 2022 11:38:11 -0500 [thread overview]
Message-ID: <1ecf05ab-b1f7-d0be-fac4-7941a306aa42@gmail.com> (raw)
In-Reply-To: <20220824153256.1437483-1-thierry.reding@gmail.com>
On 8/24/22 10:32, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> Since the stub version of of_dma_configure_id() was added in commit
> a081bd4af4ce ("of/device: Add input id to of_dma_configure()"), it has
> not matched the signature of the full function, leading to build failure
> reports when code using this function is built on !OF configurations.
>
> Fixes: a081bd4af4ce ("of/device: Add input id to of_dma_configure()")
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> include/linux/of_device.h | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/of_device.h b/include/linux/of_device.h
> index 1d7992a02e36..1a803e4335d3 100644
> --- a/include/linux/of_device.h
> +++ b/include/linux/of_device.h
> @@ -101,8 +101,9 @@ static inline struct device_node *of_cpu_device_node_get(int cpu)
> }
>
> static inline int of_dma_configure_id(struct device *dev,
> - struct device_node *np,
> - bool force_dma)
> + struct device_node *np,
> + bool force_dma,
> + const u32 *id)
> {
> return 0;
> }
Reviewed-by: Frank Rowand <frank.rowand@sony.com>
next prev parent reply other threads:[~2022-08-25 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 15:32 [PATCH] of/device: Fix up of_dma_configure_id() stub Thierry Reding
2022-08-25 10:11 ` Lorenzo Pieralisi
2022-08-25 16:38 ` Frank Rowand [this message]
2022-08-25 19:00 ` Rob Herring
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=1ecf05ab-b1f7-d0be-fac4-7941a306aa42@gmail.com \
--to=frowand.list@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).