From: Dhruva Gole <d-gole@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: Praneeth <praneeth@ti.com>, Vignesh <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] firmware: ti_sci: Fix few compiler warnings
Date: Wed, 21 Jun 2023 14:04:12 +0530 [thread overview]
Message-ID: <2d15ea8e-b2d8-2ee7-ba66-7ed6e4237cb3@ti.com> (raw)
In-Reply-To: <20230621082309.1569239-1-d-gole@ti.com>
Oops, seems like I missed similar patch,
On 21/06/23 13:53, Dhruva Gole wrote:
> Fix below warnings:
>
> CC drivers/firmware/ti_sci.o
> drivers/firmware/ti_sci.c:1988: warning: Excess function parameter 'vint_irq' description in 'ti_sci_cmd_set_irq'
> drivers/firmware/ti_sci.c:2036: warning: Excess function parameter 'vint_irq' description in 'ti_sci_cmd_free_irq'
> drivers/firmware/ti_sci.c:2632: warning: Function parameter or member
> ...
> drivers/firmware/ti_sci.c:2748: warning: expecting prototype for ti_sci_cmd_get_boot_status(). Prototype was for ti_sci_cmd_proc_get_status() instead
> drivers/firmware/ti_sci.c:3267: warning: Function parameter or member 'sub_type' not described in 'devm_ti_sci_get_resource'
> drivers/firmware/ti_sci.c:3267: warning: Excess function parameter 'suub_type' description in 'devm_ti_sci_get_resource'
>
> Fixes: 1e407f337f40 ("firmware: ti_sci: Add support for processor control")
> Signed-off-by: Dhruva Gole <d-gole@ti.com>
> ---
Nishanth already submitted this before I did,
https://lore.kernel.org/all/20230621021619.265162-1-nm@ti.com/
--
Thanks and Regards,
Dhruva Gole
_______________________________________________
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:[~2023-06-21 8:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 8:23 [PATCH] firmware: ti_sci: Fix few compiler warnings Dhruva Gole
2023-06-21 8:34 ` Dhruva Gole [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=2d15ea8e-b2d8-2ee7-ba66-7ed6e4237cb3@ti.com \
--to=d-gole@ti.com \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=praneeth@ti.com \
--cc=ssantosh@kernel.org \
--cc=vigneshr@ti.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