public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Georgi Djakov <djakov@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the icc tree
Date: Thu, 18 Aug 2022 08:00:51 +0300	[thread overview]
Message-ID: <47aa5e68-a41c-bb22-bce6-ab11a33b3d9c@kernel.org> (raw)
In-Reply-To: <20220818115326.407aa3e0@canb.auug.org.au>

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


  reply	other threads:[~2022-08-18  5:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-18  1:53 linux-next: build failure after merge of the icc tree Stephen Rothwell
2022-08-18  5:00 ` Georgi Djakov [this message]
2022-08-18  6:49   ` Uwe Kleine-König
2022-08-18  7:44     ` Georgi Djakov

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=47aa5e68-a41c-bb22-bce6-ab11a33b3d9c@kernel.org \
    --to=djakov@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=u.kleine-koenig@pengutronix.de \
    /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