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;
MIME-Version: 1.0
References: <CAHk-=wiPd8R8-zSqTOtJ9KYeZLBByHug7ny3rgP-ZqzpP_KELg@mail.gmail.com>
 <20230320180501.GA598084@dev-arch.thelio-3990X>
In-Reply-To: <20230320180501.GA598084@dev-arch.thelio-3990X>
From:   Daniel Vetter <daniel@ffwll.ch>
Date:   Fri, 24 Mar 2023 10:41:36 +0100
Message-ID: <CAKMK7uEvAQ53iSdVesR1+vFm0X03dqZU_sRkuMv0FVvg_pCF4g@mail.gmail.com>
Subject: Re: Linux 6.3-rc3
To:     Nathan Chancellor <nathan@kernel.org>
Cc:     Linus Torvalds <torvalds@linux-foundation.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        David Airlie <airlied@gmail.com>,
        dri-devel@lists.freedesktop.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Mon, 20 Mar 2023 at 19:05, Nathan Chancellor <nathan@kernel.org> wrote:
>
> On Sun, Mar 19, 2023 at 01:50:21PM -0700, Linus Torvalds wrote:
> > So rc3 is fairly big, but that's not hugely usual: it's when a lot of
> > the fixes tick up as it takes a while before people find and start
> > reporting issues.
>
> ...
>
> > Please test and report any issues you find,
>
> On the clang front, I am still seeing the following warning turned error
> for arm64 allmodconfig at least:
>
>   drivers/gpu/host1x/dev.c:520:6: error: variable 'syncpt_irq' is uninitialized when used here [-Werror,-Wuninitialized]
>           if (syncpt_irq < 0)
>               ^~~~~~~~~~
>   drivers/gpu/host1x/dev.c:490:16: note: initialize the variable 'syncpt_irq' to silence this warning
>           int syncpt_irq;
>                         ^
>                          = 0
>   1 error generated.
>
> There is an obvious fix that has been available on the mailing list for
> some time:
>
> https://lore.kernel.org/20230127221418.2522612-1-arnd@kernel.org/
>
> It appears there was some sort of process snafu, since the fix never got
> applied to the drm tree before the main pull for 6.3 and I have not been
> able to get anyone to apply it to a tree targeting -rc releases.
>
> https://lore.kernel.org/Y%2FeULFO4jbivQ679@dev-arch.thelio-3990X/
> https://lore.kernel.org/67f9fe7f-392a-9acd-1a4d-0a43da634367@nvidia.com/
>
> If that does not come to you through other means before -rc4, could you
> just apply it directly so that I can stop applying it to our CI? :)

I'll include it in the next drm-fixes pull.
-Daniel

>
> Cheers,
> Nathan


-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch