)]}'
{
  "commit": "9d433c89a2f6c345f5b48a8e01777f76229cdcc1",
  "tree": "71c9e429be9ec414224050cac1f5d2e8779f4772",
  "parents": [
    "63e9fb61908ccb0ca76c4cecbe7f38e82bbcfed3"
  ],
  "author": {
    "name": "Christopher Friedt",
    "email": "chrisfriedt@gmail.com",
    "time": "Wed Jun 22 16:17:50 2022 -0400"
  },
  "committer": {
    "name": "Carles Cufí",
    "email": "carles.cufi@nordicsemi.no",
    "time": "Fri Jun 24 20:12:05 2022 +0200"
  },
  "message": "lib: posix: semaphore: use consistent timebase in sem_timedwait\n\nIn the Zephyr implementation, `sem_timedwait()` uses a\npotentially wildly different timebase for comparison via\n`k_uptime_get()` (uptime in ms).\n\nThe standard specifies `CLOCK_REALTIME`. However, the real-time\nclock can be modified to an arbitrary value via clock_settime()\nand there is no guarantee that it will always reflect uptime.\n\nThis change ensures that `sem_timedwait()` uses a more\nconsistent timebase for comparison.\n\nFixes #46807\n\nSigned-off-by: Christopher Friedt \u003cchrisfriedt@gmail.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ffbd75f2c2787fc9be2c72f4c6dd3a02d929d769",
      "old_mode": 33188,
      "old_path": "lib/posix/Kconfig",
      "new_id": "8bb56649e3993499bb6ced5851f28329f96ae6a3",
      "new_mode": 33188,
      "new_path": "lib/posix/Kconfig"
    },
    {
      "type": "modify",
      "old_id": "778e86f5feef3cbb0c9dee8f97ef157c0de45095",
      "old_mode": 33188,
      "old_path": "lib/posix/semaphore.c",
      "new_id": "7a1392cd5211383285acc5a3f22b602ac357bfef",
      "new_mode": 33188,
      "new_path": "lib/posix/semaphore.c"
    },
    {
      "type": "modify",
      "old_id": "b884d633797596fd691546870a7cfe66f7cd2a13",
      "old_mode": 33188,
      "old_path": "samples/net/sockets/socketpair/prj.conf",
      "new_id": "4f5d22d808b59e49f597a27a159fdfee14dcbf91",
      "new_mode": 33188,
      "new_path": "samples/net/sockets/socketpair/prj.conf"
    }
  ]
}