From: David Sterba <dsterba@suse.cz>
To: Ammar Faizi <ammarfaizi2@gnuweeb.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
David Sterba <dsterba@suse.com>, Qu Wenruo <wqu@suse.com>,
Josef Bacik <josef@toxicpanda.com>, Memet <zxce3@gnuweeb.org>,
Linux Btrfs Mailing List <linux-btrfs@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>
Subject: Re: [GIT PULL] Btrfs updates for 6.3
Date: Tue, 25 Apr 2023 16:54:12 +0200 [thread overview]
Message-ID: <20230425145412.GC19619@suse.cz> (raw)
In-Reply-To: <4b35f3a4-9972-b7f0-287f-165a817c0f73@gnuweeb.org>
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@suse.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.
next prev parent reply other threads:[~2023-04-25 14:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 19:20 [GIT PULL] Btrfs updates for 6.3 David Sterba
2023-02-20 21:02 ` Linus Torvalds
2023-04-23 2:27 ` Ammar Faizi
2023-04-25 14:54 ` David Sterba [this message]
2023-04-28 3:14 ` Ammar Faizi
2023-04-28 7:34 ` Greg Kroah-Hartman
2023-02-20 21:11 ` pr-tracker-bot
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=20230425145412.GC19619@suse.cz \
--to=dsterba@suse.cz \
--cc=ammarfaizi2@gnuweeb.org \
--cc=dsterba@suse.com \
--cc=gwml@vger.gnuweeb.org \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=wqu@suse.com \
--cc=zxce3@gnuweeb.org \
/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