From: Nishanth Menon <nm@ti.com>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: Tero Kristo <kristo@kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] firmware: ti_sci: Fix devm_ti_sci_get_resource() stub
Date: Fri, 25 Mar 2022 14:51:40 -0500 [thread overview]
Message-ID: <20220325195140.ox2kyh5eet72qofa@camcorder> (raw)
In-Reply-To: <20220323184047.3931367-1-p.zabel@pengutronix.de>
On 19:40-20220323, Philipp Zabel wrote:
[...]
> diff --git a/include/linux/soc/ti/ti_sci_protocol.h b/include/linux/soc/ti/ti_sci_protocol.h
> index 0aad7009b50e..bd0d11af76c5 100644
> --- a/include/linux/soc/ti/ti_sci_protocol.h
> +++ b/include/linux/soc/ti/ti_sci_protocol.h
> @@ -645,7 +645,7 @@ devm_ti_sci_get_of_resource(const struct ti_sci_handle *handle,
>
> static inline struct ti_sci_resource *
> devm_ti_sci_get_resource(const struct ti_sci_handle *handle, struct device *dev,
> - u32 dev_id, u32 sub_type);
> + u32 dev_id, u32 sub_type)
Thanks for catching this..
However, I think we already applied this patch and is already part of
the PR we sent for 5.18
See [1] which should be Commit 043cfff99a18 ("firmware: ti_sci: Fix
compilation failure when CONFIG_TI_SCI_PROTOCOL is not defined") in
Linus-master.
[1] https://lore.kernel.org/all/e6c3cb793e1a6a2a0ae2528d5a5650dfe6a4b6ff.1640276505.git.christophe.jaillet@wanadoo.fr/
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-03-25 19:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 18:40 [PATCH] firmware: ti_sci: Fix devm_ti_sci_get_resource() stub Philipp Zabel
2022-03-25 19:51 ` Nishanth Menon [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=20220325195140.ox2kyh5eet72qofa@camcorder \
--to=nm@ti.com \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=p.zabel@pengutronix.de \
--cc=ssantosh@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