[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACMJSeu+fUdYoxue-q=DxFdvtopgshQY+i2kpZMP-RGOTqMu_g@mail.gmail.com>
Date: Tue, 23 Apr 2024 09:53:58 +0200
From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Bartosz Golaszewski <brgl@...ev.pl>, Prathamesh Shete <pshete@...dia.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the gpio-brgl-fixes tree
On Tue, 23 Apr 2024 at 01:34, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Hi all,
>
> After merging the gpio-brgl-fixes tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/gpio/gpio-tegra186.c: In function 'tegra186_gpio_is_accessible':
> drivers/gpio/gpio-tegra186.c:189:14: error: 'or' of unmatched not-equal tests is always 1 [-Werror]
> 189 | (value & TEGRA186_GPIO_WRITE_ACCESS)))
> | ^
> drivers/gpio/gpio-tegra186.c:189:14: error: 'or' of unmatched not-equal tests is always 1 [-Werror]
> cc1: all warnings being treated as errors
>
> Caused by commit
>
> 62326f7cefc2 ("gpio: tegra186: Fix tegra186_gpio_is_accessible() check")
>
> I have used the gpio-brgl-fixes tree from next-20240422 for today.
>
> --
> Cheers,
> Stephen Rothwell
I will back this out of my branch, please resend a fixed version.
Bart
Powered by blists - more mailing lists