)]}'
{
  "commit": "4fdca622c4ccaf979733e40b5a726a9f16523d32",
  "tree": "ff2ef8bb70344945605c72b6444127224117b6dc",
  "parents": [
    "9837df9064050c1e475e3b55c84ca29a8c996f06"
  ],
  "author": {
    "name": "Vlastimil Babka",
    "email": "vbabka@suse.cz",
    "time": "Fri Nov 11 11:04:55 2022 +0100"
  },
  "committer": {
    "name": "Vlastimil Babka",
    "email": "vbabka@suse.cz",
    "time": "Wed Nov 16 18:53:56 2022 +0100"
  },
  "message": "mm, slob: rename CONFIG_SLOB to CONFIG_SLOB_DEPRECATED\n\nAs explained in [1], we would like to remove SLOB if possible.\n\n- There are no known users that need its somewhat lower memory footprint\n  so much that they cannot handle SLUB instead.\n\n- It is an extra maintenance burden, and a number of features are\n  incompatible with it.\n\n- It blocks the API improvement of allowing kfree() on objects allocated\n  via kmem_cache_alloc().\n\nAs the first step, rename the CONFIG_SLOB option in the slab allocator\nconfiguration choice to CONFIG_SLOB_DEPRECATED. Add CONFIG_SLOB\ndepending on CONFIG_SLOB_DEPRECATED as an internal option to avoid code\nchurn. This will cause existing .config files and defconfigs with\nCONFIG_SLOB\u003dy to silently switch to the default (and recommended\nreplacement) SLUB, while still allowing SLOB to be configured by anyone\nthat notices and needs it. But those should contact the slab maintainers\nand linux-mm@kvack.org as explained in the updated help. With no valid\nobjections, the plan is to update the existing defconfigs to SLUB and\nremove SLOB in a few cycles.\n\n[1] https://lore.kernel.org/all/b35c3f82-f67b-2103-7d82-7a7ba7521439@suse.cz/\n\nSigned-off-by: Vlastimil Babka \u003cvbabka@suse.cz\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "39789a587011f444e3bbd5a07d961cb426af111d",
      "old_mode": 33188,
      "old_path": "mm/Kconfig",
      "new_id": "db096d3dc174a35bb3cdb5a5897f7dd75b447640",
      "new_mode": 33188,
      "new_path": "mm/Kconfig"
    }
  ]
}