From: LEROY Christophe <christophe.leroy2@cs-soprasteria.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
"qiang.zhao@nxp.com" <qiang.zhao@nxp.com>,
"leoyang.li@nxp.com" <leoyang.li@nxp.com>,
"nathan@kernel.org" <nathan@kernel.org>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Tom Rix <trix@redhat.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"llvm@lists.linux.dev" <llvm@lists.linux.dev>
Subject: Re: [PATCH v2] soc: fsl: qe: remove unused qe_ic_from_irq function
Date: Fri, 9 May 2025 16:16:13 +0000 [thread overview]
Message-ID: <f2fe43f3-fb71-4e07-a7c9-2cf151fcdbd1@cs-soprasteria.com> (raw)
In-Reply-To: <174680087395.258053.1870729490363422870.b4-ty@linaro.org>
Le 09/05/2025 à 16:28, Krzysztof Kozlowski a écrit :
>
> On Mon, 20 Mar 2023 08:52:02 -0400, Tom Rix wrote:
>> clang with W=1 reports
>> drivers/soc/fsl/qe/qe_ic.c:235:29: error: unused function
>> 'qe_ic_from_irq' [-Werror,-Wunused-function]
>> static inline struct qe_ic *qe_ic_from_irq(unsigned int virq)
>> ^
>> The use of this function was removed with
>> commit d7c2878cfcfa ("soc: fsl: qe: remove unused qe_ic_set_* functions")
>>
>> [...]
>
>
> Commit from 2021:
> https://lore.kernel.org/all/1619002613-18216-1-git-send-email-jiapeng.chong@linux.alibaba.com/
>
> did not apply, but this applies.
>
> I am annoying hitting this warning on every W=1 build, so:
Acked-by: Christophe Leroy <christophe.leroy@csgroup.eu>
>
> Applied, thanks!
>
> [1/1] soc: fsl: qe: remove unused qe_ic_from_irq function
> https://git.kernel.org/krzk/linux-dt/c/d47f1233374597c348696c3da2142cc92a36fc90
>
> Best regards,
next prev parent reply other threads:[~2025-05-09 16:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 12:52 Tom Rix
2023-03-20 13:42 ` Christophe Leroy
2025-05-09 14:28 ` Krzysztof Kozlowski
2025-05-09 16:16 ` LEROY Christophe [this message]
2025-05-09 16:16 ` Christophe Leroy
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=f2fe43f3-fb71-4e07-a7c9-2cf151fcdbd1@cs-soprasteria.com \
--to=christophe.leroy2@cs-soprasteria.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=qiang.zhao@nxp.com \
--cc=trix@redhat.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
all inboxes | Powered by JetHome®