[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230425145412.GC19619@suse.cz>
Date: Tue, 25 Apr 2023 16:54:12 +0200
From: David Sterba <dsterba@...e.cz>
To: Ammar Faizi <ammarfaizi2@...weeb.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
David Sterba <dsterba@...e.com>, Qu Wenruo <wqu@...e.com>,
Josef Bacik <josef@...icpanda.com>, Memet <zxce3@...weeb.org>,
Linux Btrfs Mailing List <linux-btrfs@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
GNU/Weeb Mailing List <gwml@...r.gnuweeb.org>
Subject: Re: [GIT PULL] Btrfs updates for 6.3
On Sun, Apr 23, 2023 at 09:27:30AM +0700, Ammar Faizi wrote:
> On 2/21/23 4:02 AM, Linus Torvalds wrote:
> > On Mon, Feb 20, 2023 at 11:26 AM David Sterba <dsterba@...e.com> wrote:
> >> Other:
> >>
> >> - locally enable -Wmaybe-uninitialized after fixing all warnings
> >
> > I've pulled this, but I strongly suspect this change will get reverted.
> >
> > I bet neither you nor linux-next is testing even _remotely_ a big
> > chunk of the different compiler versions that are out there, and the
> > reason flags like '-Wmaybe-uninitialized' get undone is because some
> > random compiler version on some random config and target archiecture
> > gives completely nonsensical warnings for odd reasons.
> >
> > But hey, maybe the btrfs code is special.
>
> Maybe it's too late for 6.3. So please fix this in 6.4 and backport it to
> 6.3 stable. If someone fixes it, kindly add:
Fix for this warning is in 6.4 pull request, there's no CC:stable tag
but we can ask to add it once the code lands in master.
Powered by blists - more mailing lists