<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/source/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>1ba19a6ea9f27ea383560d3ead6d8f5b773aff33 - btrfs: tests: zoned: add tests cases for zoned code</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/btrfs/Makefile#1ba19a6ea9f27ea383560d3ead6d8f5b773aff33</link>
        <description>btrfs: tests: zoned: add tests cases for zoned codeAdd a test function for the zoned code, for now it testsbtrfs_load_block_group_by_raid_type() with various test cases. Theload_zone_info_tests[] array defines the test cases.Signed-off-by: Naohiro Aota &lt;naohiro.aota@wdc.com&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux/fs/btrfs/Makefile</description>
        <pubDate>Wed, 04 Feb 2026 08:31:25 +0100</pubDate>
        <dc:creator>Naohiro Aota &lt;naohiro.aota@wdc.com&gt;</dc:creator>
    </item>
<item>
        <title>41f1a08645abb5ef7d2a3ed8835c747334878774 - Merge tag &apos;kbuild-7.0-1&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/btrfs/Makefile#41f1a08645abb5ef7d2a3ed8835c747334878774</link>
        <description>Merge tag &apos;kbuild-7.0-1&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linuxPull Kbuild/Kconfig updates from Nathan Chancellor: &quot;Kbuild:   - Drop &apos;*_probe&apos; pattern from modpost section check allowlist, which     hid legitimate warnings (Johan Hovold)   - Disable -Wtype-limits altogether, instead of enabling at W=2     (Vincent Mailhol)   - Improve UAPI testing to skip testing headers that require a libc     when CONFIG_CC_CAN_LINK is not set, opening up testing of headers     with no libc dependencies to more environments (Thomas Wei&#223;schuh)   - Update gendwarfksyms documentation with required dependencies     (Jihan LIN)   - Reject invalid LLVM= values to avoid unintentionally falling back     to system toolchain (Thomas Wei&#223;schuh)   - Add a script to help run the kernel build process in a container     for consistent environments and testing (Guillaume Tucker)   - Simplify kallsyms by getting rid of the relative base (Ard     Biesheuvel)   - Performance and usability improvements to scripts/make_fit.py     (Simon Glass)   - Minor various clean ups and fixes  Kconfig:   - Move XPM icons to individual files, clearing up GTK deprecation     warnings (Rostislav Krasny)   - Support        depends on FOO if BAR     as syntactic sugar for        depends on FOO || !BAR     (Nicolas Pitre, Graham Roff)   - Refactor merge_config.sh to use awk over shell/sed/grep,     dramatically speeding up processing large number of config     fragments (Anders Roxell, Mikko Rapeli)&quot;* tag &apos;kbuild-7.0-1&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux: (39 commits)  kbuild: remove dependency of run-command on config  scripts/make_fit: Compress dtbs in parallel  scripts/make_fit: Support a few more parallel compressors  kbuild: Support a FIT_EXTRA_ARGS environment variable  scripts/make_fit: Move dtb processing into a function  scripts/make_fit: Support an initial ramdisk  scripts/make_fit: Speed up operation  rust: kconfig: Don&apos;t require RUST_IS_AVAILABLE for rustc-option  MAINTAINERS: Add scripts/install.sh into Kbuild entry  modpost: Amend ppc64 save/restfpr symnames for -Os build  MIPS: tools: relocs: Ship a definition of R_MIPS_PC32  streamline_config.pl: remove superfluous exclamation mark  kbuild: dummy-tools: Add python3  scripts: kconfig: merge_config.sh: warn on duplicate input files  scripts: kconfig: merge_config.sh: use awk in checks too  scripts: kconfig: merge_config.sh: refactor from shell/sed/grep to awk  kallsyms: Get rid of kallsyms relative base  mips: Add support for PC32 relocations in vmlinux  Documentation: dev-tools: add container.rst page  scripts: add tool to run containerized builds  ...

            List of files:
            /linux/fs/btrfs/Makefile</description>
        <pubDate>Wed, 11 Feb 2026 22:40:35 +0100</pubDate>
        <dc:creator>Linus Torvalds &lt;torvalds@linux-foundation.org&gt;</dc:creator>
    </item>
<item>
        <title>5341c98450df7cf8dacc907a80e3362f3155c847 - btrfs: tests: add unit tests for pending extent walking functions</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/btrfs/Makefile#5341c98450df7cf8dacc907a80e3362f3155c847</link>
        <description>btrfs: tests: add unit tests for pending extent walking functionsI ran into another sort of trivial bug in v1 of the patch and concludedthat these functions really ought to be unit tested.These two functions form the core of searching the chunk allocationpending extent bitmap and have relatively easily definable semantics, sounit testing them can help ensure the correctness of chunk allocation.I also made a minor unrelated fix in volumes.h to properly forwarddeclare btrfs_space_info. Because of the order of the includes in thenew test, this was actually hitting a latent build warning.Note:This is an early example for me of a commit authored in part by an AIagent, so I wanted to more clear about what I did. I defined atrivial test and explained the set of tests I wanted to the agent and itproduced the large set of test cases seen here. I then checked each testcase to make sure it matched the description and simplified theconstants and numbers until they looked reasonable to me. I then checkedthe looping logic to make sure it made sense to the original spirit ofthe trivial test. Finally, carefully combed over all the lines it wroteto loop over the tests it generated to make sure they followed our codestyle guide.Assisted-by: Claude:claude-opus-4-5Signed-off-by: Boris Burkov &lt;boris@bur.io&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux/fs/btrfs/Makefile</description>
        <pubDate>Fri, 30 Jan 2026 01:11:22 +0100</pubDate>
        <dc:creator>Boris Burkov &lt;boris@bur.io&gt;</dc:creator>
    </item>
<item>
        <title>34a1bd0b6b2c03206f3ca629eafd2cad95fd6b22 - kbuild: cleanup local -Wno-type-limits exceptions</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/btrfs/Makefile#34a1bd0b6b2c03206f3ca629eafd2cad95fd6b22</link>
        <description>kbuild: cleanup local -Wno-type-limits exceptionsNow that -Wtype-limits is globally deactivated, there is no need forlocal exceptions anymore.Acked-by: David Sterba &lt;dsterba@suse.com&gt;Signed-off-by: Vincent Mailhol &lt;mailhol@kernel.org&gt;Reviewed-by: Nicolas Schier &lt;nsc@kernel.org&gt;Link: https://patch.msgid.link/20251220-remove_wtype-limits-v3-2-24b170af700e@kernel.orgSigned-off-by: Nathan Chancellor &lt;nathan@kernel.org&gt;

            List of files:
            /linux/fs/btrfs/Makefile</description>
        <pubDate>Sat, 20 Dec 2025 12:02:20 +0100</pubDate>
        <dc:creator>Vincent Mailhol &lt;mailhol@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>cba7c35fec267188a9708deae857e9116c57497b - btrfs: move ref-verify under CONFIG_BTRFS_DEBUG</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/btrfs/Makefile#cba7c35fec267188a9708deae857e9116c57497b</link>
        <description>btrfs: move ref-verify under CONFIG_BTRFS_DEBUGRemove CONFIG_BTRFS_FS_REF_VERIFY Kconfig and add it as part ofCONFIG_BTRFS_DEBUG. This should not be impactful to the performanceof debug. The struct btrfs_ref takes an additional u64, btrfs_fs_infotakes an additional spinlock_t and rb_root. All of the ref_verify logicis still protected by a mount option.Signed-off-by: Leo Martins &lt;loemra.dev@gmail.com&gt;Reviewed-by: David Sterba &lt;dsterba@suse.com&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux/fs/btrfs/Makefile</description>
        <pubDate>Wed, 13 Aug 2025 01:28:27 +0200</pubDate>
        <dc:creator>Leo Martins &lt;loemra.dev@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>2b34879d97e27b74e8e933463f5e9073d9d39821 - btrfs: selftests: add delayed ref self test cases</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/btrfs/Makefile#2b34879d97e27b74e8e933463f5e9073d9d39821</link>
        <description>btrfs: selftests: add delayed ref self test casesThe recent fix for a stupid mistake I made uncovered the fact that wedon&apos;t have adequate testing in the delayed refs code, as it took apretty extensive and long running stress test to uncover something thata unit test would have uncovered right away.Fix this by adding a delayed refs self test suite.  This will validatethat the btrfs_ref transformation does the correct thing, that we do thecorrect thing when merging delayed refs, and that we get the delayedrefs in the order that we expect.  These are all crucial to how thedelayed refs operate.I introduced various bugs (including the original bug) into the delayedrefs code to validate that these tests caught all of the shenanigansthat I could think of.Reviewed-by: Boris Burkov &lt;boris@bur.io&gt;Signed-off-by: Josef Bacik &lt;josef@toxicpanda.com&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux/fs/btrfs/Makefile</description>
        <pubDate>Thu, 14 Nov 2024 16:03:34 +0100</pubDate>
        <dc:creator>Josef Bacik &lt;josef@toxicpanda.com&gt;</dc:creator>
    </item>
<item>
        <title>506be4d5657569e7683cad9de17f980d264a60ec - btrfs: tests: add selftests for raid-stripe-tree</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/btrfs/Makefile#506be4d5657569e7683cad9de17f980d264a60ec</link>
        <description>btrfs: tests: add selftests for raid-stripe-treeAdd first stash of very basic self tests for the RAID stripe-tree.More test cases will follow exercising the tree.Reviewed-by: Filipe Manana &lt;fdmanana@suse.com&gt;Signed-off-by: Johannes Thumshirn &lt;johannes.thumshirn@wdc.com&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux/fs/btrfs/Makefile</description>
        <pubDate>Wed, 02 Oct 2024 12:11:48 +0200</pubDate>
        <dc:creator>Johannes Thumshirn &lt;johannes.thumshirn@wdc.com&gt;</dc:creator>
    </item>
<item>
        <title>9aa29a20b70097213d10e03a452366ceea72fc02 - btrfs: move the direct IO code into its own file</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/btrfs/Makefile#9aa29a20b70097213d10e03a452366ceea72fc02</link>
        <description>btrfs: move the direct IO code into its own fileThe direct IO code is over a thousand lines and it&apos;s currently spreadbetween file.c and inode.c, which makes it not easy to locate some partsof it sometimes. Also inode.c is about 11 thousand lines and file.c about4 thousand lines, both too big. So move all the direct IO code into adedicated file, so that it&apos;s easy to locate all its code and reduce thesizes of inode.c and file.c.This is a pure move of code without any other changes except export aa couple functions from inode.c (get_extent_allocation_hint() andcreate_io_em()) because they are used in inode.c and the new direct-io.cfile, and a couple functions from file.c (btrfs_buffered_write() andbtrfs_write_check()) because they are used both in file.c and in the newdirect-io.c file.Reviewed-by: Boris Burkov &lt;boris@bur.io&gt;Reviewed-by: Qu Wenruo &lt;wqu@suse.com&gt;Signed-off-by: Filipe Manana &lt;fdmanana@suse.com&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux/fs/btrfs/Makefile</description>
        <pubDate>Tue, 25 Jun 2024 16:52:28 +0200</pubDate>
        <dc:creator>Filipe Manana &lt;fdmanana@suse.com&gt;</dc:creator>
    </item>
<item>
        <title>8996f61ab9ff06a1433a58dd67ea0bf6f91ba499 - btrfs: move fiemap code into its own file</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/btrfs/Makefile#8996f61ab9ff06a1433a58dd67ea0bf6f91ba499</link>
        <description>btrfs: move fiemap code into its own fileCurrently the core of the fiemap code lives in extent_io.c, which doesnot make any sense because it&apos;s not related to extent IO at all (and itwas not as well before the big rewrite of fiemap I did some time ago).The entry point for fiemap, btrfs_fiemap(), lives in inode.c since it&apos;san inode operation.Since there&apos;s a significant amount of fiemap code, move all of it into adedicated file, including its entry point inode.c:btrfs_fiemap().Reviewed-by: Johannes Thumshirn &lt;johannes.thumshirn@wdc.com&gt;Signed-off-by: Filipe Manana &lt;fdmanana@suse.com&gt;Reviewed-by: David Sterba &lt;dsterba@suse.com&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux/fs/btrfs/Makefile</description>
        <pubDate>Wed, 22 May 2024 16:29:05 +0200</pubDate>
        <dc:creator>Filipe Manana &lt;fdmanana@suse.com&gt;</dc:creator>
    </item>
<item>
        <title>02c372e1f016e5113217597ab37b399c4e407477 - btrfs: add support for inserting raid stripe extents</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/btrfs/Makefile#02c372e1f016e5113217597ab37b399c4e407477</link>
        <description>btrfs: add support for inserting raid stripe extentsAdd support for inserting stripe extents into the raid stripe tree oncompletion of every write that needs an extra logical-to-physicaltranslation when using RAID.Inserting the stripe extents happens after the data I/O has completed,this is done to  a) support zone-append and  b) rule out the possibility of a RAID-write-hole.Signed-off-by: Johannes Thumshirn &lt;johannes.thumshirn@wdc.com&gt;Reviewed-by: David Sterba &lt;dsterba@suse.com&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux/fs/btrfs/Makefile</description>
        <pubDate>Thu, 14 Sep 2023 18:06:58 +0200</pubDate>
        <dc:creator>Johannes Thumshirn &lt;johannes.thumshirn@wdc.com&gt;</dc:creator>
    </item>
<item>
        <title>fb2a836da4513cb2e0d9bb8548f3f095a814dda5 - btrfs: check-integrity: remove btrfsic_unmount() function</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/btrfs/Makefile#fb2a836da4513cb2e0d9bb8548f3f095a814dda5</link>
        <description>btrfs: check-integrity: remove btrfsic_unmount() functionThe function btrfsic_mount() is part of the deprecated check-integrityfunctionality.Now let&apos;s remove the main entry point of check-integrity, and thankfullymost of the check-integrity code is self-contained insidecheck-integrity.c, we can safely remove the function without hugechanges to btrfs code base.Signed-off-by: Qu Wenruo &lt;wqu@suse.com&gt;Reviewed-by: David Sterba &lt;dsterba@suse.com&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux/fs/btrfs/Makefile</description>
        <pubDate>Fri, 08 Sep 2023 08:42:16 +0200</pubDate>
        <dc:creator>Qu Wenruo &lt;wqu@suse.com&gt;</dc:creator>
    </item>
<item>
        <title>90b90d4ac03cbaaa87a81ee04e9cdd9b4225cdd4 - btrfs: send: genericize the backref cache to allow it to be reused</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/btrfs/Makefile#90b90d4ac03cbaaa87a81ee04e9cdd9b4225cdd4</link>
        <description>btrfs: send: genericize the backref cache to allow it to be reusedThe backref cache is a cache backed by a maple tree and a linked list tokeep track of temporal access to cached entries (the LRU entry always atthe head of the list). This type of caching method is going to be usefulin other scenarios, so make the cache implementation more generic andmove it into its own header and source files.This patch is part of a larger patchset and the changelog of the lastpatch in the series contains a sample performance test and results.The patches that comprise the patchset are the following:  btrfs: send: directly return from did_overwrite_ref() and simplify it  btrfs: send: avoid unnecessary generation search at did_overwrite_ref()  btrfs: send: directly return from will_overwrite_ref() and simplify it  btrfs: send: avoid extra b+tree searches when checking reference overrides  btrfs: send: remove send_progress argument from can_rmdir()  btrfs: send: avoid duplicated orphan dir allocation and initialization  btrfs: send: avoid unnecessary orphan dir rbtree search at can_rmdir()  btrfs: send: reduce searches on parent root when checking if dir can be removed  btrfs: send: iterate waiting dir move rbtree only once when processing refs  btrfs: send: initialize all the red black trees earlier  btrfs: send: genericize the backref cache to allow it to be reused  btrfs: adapt lru cache to allow for 64 bits keys on 32 bits systems  btrfs: send: cache information about created directories  btrfs: allow a generation number to be associated with lru cache entries  btrfs: add an api to delete a specific entry from the lru cache  btrfs: send: use the lru cache to implement the name cache  btrfs: send: update size of roots array for backref cache entries  btrfs: send: cache utimes operations for directories if possibleSigned-off-by: Filipe Manana &lt;fdmanana@suse.com&gt;Reviewed-by: David Sterba &lt;dsterba@suse.com&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux/fs/btrfs/Makefile</description>
        <pubDate>Wed, 11 Jan 2023 12:36:13 +0100</pubDate>
        <dc:creator>Filipe Manana &lt;fdmanana@suse.com&gt;</dc:creator>
    </item>
<item>
        <title>1ec49744ba83f0429c5c706708610f7821a7b6f4 - btrfs: turn on -Wmaybe-uninitialized</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/btrfs/Makefile#1ec49744ba83f0429c5c706708610f7821a7b6f4</link>
        <description>btrfs: turn on -Wmaybe-uninitializedWe had a recent bug that would have been caught by a newer compiler with-Wmaybe-uninitialized and would have saved us a month of failing teststhat I didn&apos;t have time to investigate.Reviewed-by: Qu Wenruo &lt;wqu@suse.com&gt;Signed-off-by: Josef Bacik &lt;josef@toxicpanda.com&gt;Reviewed-by: David Sterba &lt;dsterba@suse.com&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux/fs/btrfs/Makefile</description>
        <pubDate>Fri, 16 Dec 2022 21:15:58 +0100</pubDate>
        <dc:creator>Josef Bacik &lt;josef@toxicpanda.com&gt;</dc:creator>
    </item>
<item>
        <title>103c19723c80bf74e4e70cd6cde3b8783a27aceb - btrfs: split the bio submission path into a separate file</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/btrfs/Makefile#103c19723c80bf74e4e70cd6cde3b8783a27aceb</link>
        <description>btrfs: split the bio submission path into a separate fileThe code used by btrfs_submit_bio only interacts with the rest ofvolumes.c through __btrfs_map_block (which itself is a more genericversion of two exported helpers) and does not really have anythingto do with volumes.c.  Create a new bio.c file and a bio.h headergoing along with it for the btrfs_bio-based storage layer, whichwill grow even more going forward.Also update the file with my copyright notice given that a largepart of the moved code was written or rewritten by me.Reviewed-by: Josef Bacik &lt;josef@toxicpanda.com&gt;Reviewed-by: Johannes Thumshirn &lt;johannes.thumshirn@wdc.com&gt;Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Reviewed-by: David Sterba &lt;dsterba@suse.com&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux/fs/btrfs/Makefile</description>
        <pubDate>Tue, 15 Nov 2022 10:44:05 +0100</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>778dd695dd4d5a21eff07bb1570b570da69dfbd9 - btrfs: rename tree-defrag.c to defrag.c</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/btrfs/Makefile#778dd695dd4d5a21eff07bb1570b570da69dfbd9</link>
        <description>btrfs: rename tree-defrag.c to defrag.cThis currently has only one helper in it, and it&apos;s for tree baseddefrag.  We have the various defrag code in 3 different places, sorename this to defrag.c.  Followup patches will move the code into thisnew file.Reviewed-by: Johannes Thumshirn &lt;johannes.thumshirn@wdc.com&gt;Signed-off-by: Josef Bacik &lt;josef@toxicpanda.com&gt;Reviewed-by: David Sterba &lt;dsterba@suse.com&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux/fs/btrfs/Makefile</description>
        <pubDate>Wed, 26 Oct 2022 21:08:22 +0200</pubDate>
        <dc:creator>Josef Bacik &lt;josef@toxicpanda.com&gt;</dc:creator>
    </item>
<item>
        <title>083bd7e54e8e2c1d169f21236873272cdf6f409a - btrfs: move the printk and assert helpers to messages.c</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/btrfs/Makefile#083bd7e54e8e2c1d169f21236873272cdf6f409a</link>
        <description>btrfs: move the printk and assert helpers to messages.cThese helpers are core to btrfs, and in order to more easily syncvarious parts of the btrfs kernel code into btrfs-progs we need to beable to carry these helpers with us.  However we want to have our ownimplementation for the helpers themselves, currently they&apos;re implementedin different files that we want to sync inside of btrfs-progs itself.Move these into their own C file, this will allow us to contain ouroverrides in btrfs-progs in it&apos;s own file without messing with the restof the codebase.In copying things over I fixed up a few whitespace errors that alreadyexisted.Signed-off-by: Josef Bacik &lt;josef@toxicpanda.com&gt;Reviewed-by: David Sterba &lt;dsterba@suse.com&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux/fs/btrfs/Makefile</description>
        <pubDate>Wed, 26 Oct 2022 21:08:20 +0200</pubDate>
        <dc:creator>Josef Bacik &lt;josef@toxicpanda.com&gt;</dc:creator>
    </item>
<item>
        <title>818fe33aed42ddd5052171328a3f708e98357e10 - btrfs: rename struct-funcs.c to accessors.c</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/btrfs/Makefile#818fe33aed42ddd5052171328a3f708e98357e10</link>
        <description>btrfs: rename struct-funcs.c to accessors.cRename struct-funcs.c to accessors.c so we can move the item accessorsout of ctree.h. accessors.c is a better description of the code that iscontained in these files.Reviewed-by: Johannes Thumshirn &lt;johannes.thumshirn@wdc.com&gt;Reviewed-by: Anand Jain &lt;anand.jain@oracle.com&gt;Signed-off-by: Josef Bacik &lt;josef@toxicpanda.com&gt;Reviewed-by: David Sterba &lt;dsterba@suse.com&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux/fs/btrfs/Makefile</description>
        <pubDate>Wed, 19 Oct 2022 16:50:58 +0200</pubDate>
        <dc:creator>Josef Bacik &lt;josef@toxicpanda.com&gt;</dc:creator>
    </item>
<item>
        <title>c7f13d428ea1bfe883f2741a9b5a5352d595eb09 - btrfs: move fs wide helpers out of ctree.h</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/btrfs/Makefile#c7f13d428ea1bfe883f2741a9b5a5352d595eb09</link>
        <description>btrfs: move fs wide helpers out of ctree.hWe have several fs wide related helpers in ctree.h.  The bulk of theseare the incompat flag test helpers, but there are things such asbtrfs_fs_closing() and the read only helpers that also aren&apos;t directlyrelated to the ctree code.  Move these into a fs.h header, which willserve as the location for file system wide related helpers.Reviewed-by: Johannes Thumshirn &lt;johannes.thumshirn@wdc.com&gt;Reviewed-by: Anand Jain &lt;anand.jain@oracle.com&gt;Signed-off-by: Josef Bacik &lt;josef@toxicpanda.com&gt;Reviewed-by: David Sterba &lt;dsterba@suse.com&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux/fs/btrfs/Makefile</description>
        <pubDate>Wed, 19 Oct 2022 16:50:47 +0200</pubDate>
        <dc:creator>Josef Bacik &lt;josef@toxicpanda.com&gt;</dc:creator>
    </item>
<item>
        <title>83cf709a89fb97e78e60f310ea5f2b283e0f581c - btrfs: move extent state init and alloc functions to their own file</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/btrfs/Makefile#83cf709a89fb97e78e60f310ea5f2b283e0f581c</link>
        <description>btrfs: move extent state init and alloc functions to their own fileStart cleaning up extent_io.c by moving the extent state code out of it.This patch starts with the extent state allocation code and theextent_io_tree init code.Signed-off-by: Josef Bacik &lt;josef@toxicpanda.com&gt;Reviewed-by: David Sterba &lt;dsterba@suse.com&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux/fs/btrfs/Makefile</description>
        <pubDate>Fri, 09 Sep 2022 23:53:21 +0200</pubDate>
        <dc:creator>Josef Bacik &lt;josef@toxicpanda.com&gt;</dc:creator>
    </item>
<item>
        <title>1344794a59db2bd44b4919d2d75300fd3b1c2cd7 - Kbuild: add -Wno-shift-negative-value where -Wextra is used</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/btrfs/Makefile#1344794a59db2bd44b4919d2d75300fd3b1c2cd7</link>
        <description>Kbuild: add -Wno-shift-negative-value where -Wextra is usedAs a preparation for moving to -std=gnu11, turn off the-Wshift-negative-value option. This warning is enabled by gcc whenbuilding with -Wextra for c99 or higher, but not for c89. Sincethe kernel already relies on well-defined overflow behavior,the warning is not helpful and can simply be disabled inall locations that use -Wextra.Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Acked-by: Jani Nikula &lt;jani.nikula@intel.com&gt;Reviewed-by: Nathan Chancellor &lt;nathan@kernel.org&gt;Tested-by: Sedat Dilek &lt;sedat.dilek@gmail.com&gt; # LLVM/Clang v13.0.0 (x86-64)Signed-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;

            List of files:
            /linux/fs/btrfs/Makefile</description>
        <pubDate>Tue, 08 Mar 2022 22:56:12 +0100</pubDate>
        <dc:creator>Arnd Bergmann &lt;arnd@arndb.de&gt;</dc:creator>
    </item>
</channel>
</rss>
