From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs build fix for 6.11
Date: Fri, 19 Jul 2024 21:08:25 +0200 [thread overview]
Message-ID: <cover.1721414023.git.dsterba@suse.com> (raw)
Hi,
please pull a fix for build breakage on 32bit platforms. I misjudged the
severity of the fix, it first looked like a functional fix that could
wait but failing subset of builds should not (-Werror=overflow). I'm not
aware of any reports from linux-next build coverage before merge window.
Thanks.
----------------------------------------------------------------
The following changes since commit 8e7860543a94784d744c7ce34b78a2e11beefa5c:
btrfs: fix extent map use-after-free when adding pages to compressed bio (2024-07-11 16:32:22 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.11-tag
for you to fetch changes up to c3ece6b7ffb4a7c00e8d53cbf4026a32b6127914:
btrfs: change BTRFS_MOUNT_* flags to 64bit type (2024-07-19 17:20:23 +0200)
----------------------------------------------------------------
Qu Wenruo (1):
btrfs: change BTRFS_MOUNT_* flags to 64bit type
fs/btrfs/fs.h | 66 ++++++++++++++++++++++++++++----------------------------
fs/btrfs/super.c | 11 +++++-----
fs/btrfs/super.h | 3 ++-
fs/btrfs/zoned.c | 3 ++-
fs/btrfs/zoned.h | 5 +++--
5 files changed, 46 insertions(+), 42 deletions(-)
next reply other threads:[~2024-07-19 19:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 19:08 David Sterba [this message]
2024-07-19 21:39 ` [GIT PULL] Btrfs build fix for 6.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=cover.1721414023.git.dsterba@suse.com \
--to=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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