)]}'
{
  "commit": "26b4692416b0454c384c99724367973b91cfb2a0",
  "tree": "ed1ff3c65c811f90b024d39bf7462790881474f6",
  "parents": [
    "62dee964d18da26e822efb2f8b2b8f7aecfd0cda"
  ],
  "author": {
    "name": "Leon Romanovsky",
    "email": "leonro@nvidia.com",
    "time": "Thu Aug 20 08:08:06 2026 -0400"
  },
  "committer": {
    "name": "Leon Romanovsky",
    "email": "leonro@nvidia.com",
    "time": "Sun Sep 06 08:30:02 2026 -0400"
  },
  "message": "dma-buf: Document how exporters and importers agree on mapping lifetime\n\nNothing in DMA-buf declares whether a mapping may be moved or taken away.\nNearly every callback on both sides is optional, so the answer follows\nfrom which ones are implemented and from whether dma_buf_pin() succeeds.\nDocumentation/ says none of this, and the rules sit in the kdoc of\ndma_buf_ops.pin, dma_buf_attach_ops.invalidate_mappings and\ndma_buf_invalidate_mappings(), which a driver author has to know by name\nbefore finding them.\n\nDescribe the three flows an importer has to handle, the callbacks each\none asks of both sides, and dma_buf_pin() as the runtime negotiation.\n\nSigned-off-by: Leon Romanovsky \u003cleonro@nvidia.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2f36c21d9948f4147496a139c36f662da455e475",
      "old_mode": 33188,
      "old_path": "Documentation/driver-api/dma-buf.rst",
      "new_id": "39c201f38aa6be1a747caa6b77e4cbd73a623fd3",
      "new_mode": 33188,
      "new_path": "Documentation/driver-api/dma-buf.rst"
    },
    {
      "type": "modify",
      "old_id": "d504c636dc294e863acdf1eba5a5850be59074fb",
      "old_mode": 33188,
      "old_path": "drivers/dma-buf/dma-buf.c",
      "new_id": "aa47142cd9ed72a990e99001882c6468e6d8c5e4",
      "new_mode": 33188,
      "new_path": "drivers/dma-buf/dma-buf.c"
    }
  ]
}