Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <47aa5e68-a41c-bb22-bce6-ab11a33b3d9c@kernel.org>
Date:   Thu, 18 Aug 2022 08:00:51 +0300
MIME-Version: 1.0
Subject: Re: linux-next: build failure after merge of the icc tree
Content-Language: en-US
To:     Stephen Rothwell <sfr@canb.auug.org.au>
Cc:     =?UTF-8?Q?Uwe_Kleine-K=c3=b6nig?= <u.kleine-koenig@pengutronix.de>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
References: <20220818115326.407aa3e0@canb.auug.org.au>
From:   Georgi Djakov <djakov@kernel.org>
In-Reply-To: <20220818115326.407aa3e0@canb.auug.org.au>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 18.08.22 4:53, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the icc tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
> 
> drivers/interconnect/imx/imx8mp.c: In function 'imx8mp_icc_remove':
> drivers/interconnect/imx/imx8mp.c:245:16: error: void value not ignored as it ought to be
>    245 |         return imx_icc_unregister(pdev);
>        |                ^~~~~~~~~~~~~~~~~~~~~~~~
> drivers/interconnect/imx/imx8mp.c:246:1: error: control reaches end of non-void function [-Werror=return-type]
>    246 | }
>        | ^
> 
> Caused by commit
> 
>    d761e0e9c8f2 ("interconnect: imx: Make imx_icc_unregister() return void")
> 
> I have used the icc tree from next-20220817 for today.

Thanks Stephen! Fixed.

BR,
Georgi