{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":638659777,"defaultBranch":"main","name":"zephyr","ownerLogin":"LuDuda","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2023-05-09T20:34:19.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/5144764?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1724006791.0","currentOid":""},"activityList":{"items":[{"before":"b6bc93360e950284f275fe8f54b8716e1072e38d","after":"4d5c9f3ab1a01e2152124b01a25a82d12597f34f","ref":"refs/heads/pr/ip-deprecation","pushedAt":"2024-08-18T19:36:53.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"LuDuda","name":"Łukasz Duda","path":"/LuDuda","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5144764?s=80&v=4"},"commit":{"message":"net: openthread: Fix the handling of address state changes\n\nThis commit ensures that the state of the address can be changed from\nthe Deprecated state to the Preferred state.\n\nAdditionally, an issue with improper memory comparison size for the mesh\nlocal prefix has been fixed.\n\nSigned-off-by: Łukasz Duda ","shortMessageHtmlLink":"net: openthread: Fix the handling of address state changes"}},{"before":null,"after":"b6bc93360e950284f275fe8f54b8716e1072e38d","ref":"refs/heads/pr/ip-deprecation","pushedAt":"2024-08-18T18:46:31.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"LuDuda","name":"Łukasz Duda","path":"/LuDuda","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5144764?s=80&v=4"},"commit":{"message":"net: openthread: Fix the handling of address state changes\n\nThis commit ensures that the state of the address can be changed from\nthe Deprecated state to the Preferred state.\n\nAdditionally, an issue with improper memory comparison size for the mesh\nlocal prefix has been fixed.\n\nSigned-off-by: Łukasz Duda ","shortMessageHtmlLink":"net: openthread: Fix the handling of address state changes"}},{"before":"fb49e5e1280fbd4e3a7e092fc676ee236a222335","after":"d1f8ec98ede400a29f69796cfab4d3ae4d192815","ref":"refs/heads/pr/ot-addr","pushedAt":"2024-08-05T06:35:54.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"LuDuda","name":"Łukasz Duda","path":"/LuDuda","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5144764?s=80&v=4"},"commit":{"message":"net: openthread: Handle deprecated IPv6 addresses correctly\n\nThis commit fixes an issue where deprecated IPv6 addresses were not\nbeing correctly marked. In some cases, deprecated addresses might have\nbeen used as source addresses.\n\nSigned-off-by: Łukasz Duda ","shortMessageHtmlLink":"net: openthread: Handle deprecated IPv6 addresses correctly"}},{"before":null,"after":"fb49e5e1280fbd4e3a7e092fc676ee236a222335","ref":"refs/heads/pr/ot-addr","pushedAt":"2024-08-04T19:24:14.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"LuDuda","name":"Łukasz Duda","path":"/LuDuda","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5144764?s=80&v=4"},"commit":{"message":"net: openthread: Handle deprecated IPv6 addresses correctly\n\nThis commit fixes an issue where deprecated IPv6 addresses were not\nbeing correctly marked. In some cases, deprecated addresses might have\nbeen used as source addresses.\n\nSigned-off-by: Łukasz Duda ","shortMessageHtmlLink":"net: openthread: Handle deprecated IPv6 addresses correctly"}},{"before":"28f7cee98c39f7117ca5b9181a61dcc1728d79f4","after":"74177484f2fa65da697d5eae22f1b0f24f4a310c","ref":"refs/heads/pr/hint-api","pushedAt":"2024-02-13T14:21:51.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"LuDuda","name":"Łukasz Duda","path":"/LuDuda","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5144764?s=80&v=4"},"commit":{"message":"net: ipv6: nbr: Expose API for reporting neighbor reachability\n\nThis commit extends Zephyr's networking API to allow higher layers to\nreport on neighbor reachability.\n\nSigned-off-by: Łukasz Duda ","shortMessageHtmlLink":"net: ipv6: nbr: Expose API for reporting neighbor reachability"}},{"before":"e72ac4b0917e259ae7ddda2dee5e25c5ea6c0978","after":"28f7cee98c39f7117ca5b9181a61dcc1728d79f4","ref":"refs/heads/pr/hint-api","pushedAt":"2024-02-13T14:19:20.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"LuDuda","name":"Łukasz Duda","path":"/LuDuda","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5144764?s=80&v=4"},"commit":{"message":"net: ipv6: nbr: Expose API for reporting neighbor reachability\n\nThis commit extends Zephyr's networking API to allow higher layers to\nreport on neighbor reachability.\n\nSigned-off-by: Łukasz Duda ","shortMessageHtmlLink":"net: ipv6: nbr: Expose API for reporting neighbor reachability"}},{"before":null,"after":"e72ac4b0917e259ae7ddda2dee5e25c5ea6c0978","ref":"refs/heads/pr/hint-api","pushedAt":"2024-02-13T14:16:55.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"LuDuda","name":"Łukasz Duda","path":"/LuDuda","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5144764?s=80&v=4"},"commit":{"message":"net: coap: add TOO_MANY_REQUESTS to return codes\n\nAdd COAP_RESPONSE_CODE_TOO_MANY_REQUESTS to coap_header_get_code(). CoAP\n4.29 response code for \"Too many requests\" is defined in coap.h but was\nmissing from the list of cases, resulting in a 0 being returned instead\nof the proper code.\n\nSigned-off-by: Mike Szczys ","shortMessageHtmlLink":"net: coap: add TOO_MANY_REQUESTS to return codes"}},{"before":"15e8ca4db4d0def34325e561233396eeee22f673","after":"0dd67ee963431bb37b08f971fa334ce4b3116601","ref":"refs/heads/pr/nd-reachability-hint-rate-limitng","pushedAt":"2024-02-08T20:14:59.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"LuDuda","name":"Łukasz Duda","path":"/LuDuda","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5144764?s=80&v=4"},"commit":{"message":"net: tcp: Rate-limiting of neighbor reachability hints\n\nThis commit implements simple rate-limiting for Neighbor Reachability\nHints in TCP module to prevent the potentially costly process of\nfrequent neighbor searches in the table, enhancing system performance.\n\nSigned-off-by: Łukasz Duda ","shortMessageHtmlLink":"net: tcp: Rate-limiting of neighbor reachability hints"}},{"before":"826eb41b5300ecfb674813e8a7fa7da422179e3d","after":"15e8ca4db4d0def34325e561233396eeee22f673","ref":"refs/heads/pr/nd-reachability-hint-rate-limitng","pushedAt":"2024-02-06T20:58:47.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"LuDuda","name":"Łukasz Duda","path":"/LuDuda","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5144764?s=80&v=4"},"commit":{"message":"net: tcp: Rate-limiting of neighbor reachability hints\n\nThis commit implements simple rate-limiting for Neighbor Reachability\nHints in TCP module to prevent the potentially costly process of\nfrequent neighbor searches in the table, enhancing system performance.\n\nSigned-off-by: Łukasz Duda ","shortMessageHtmlLink":"net: tcp: Rate-limiting of neighbor reachability hints"}},{"before":null,"after":"826eb41b5300ecfb674813e8a7fa7da422179e3d","ref":"refs/heads/pr/nd-reachability-hint-rate-limitng","pushedAt":"2024-01-31T19:41:58.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"LuDuda","name":"Łukasz Duda","path":"/LuDuda","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5144764?s=80&v=4"},"commit":{"message":"net: tcp: Rate-limiting of neighbor reachability hints\n\nThis commit implements an arbitrary chosen 5-second rate-limiting\ninterval for Neighbor Reachability Hints in TCP module to prevent the\npotentially costly process of frequent neighbor searches in the table,\nenhancing system performance.\n\nSigned-off-by: Łukasz Duda ","shortMessageHtmlLink":"net: tcp: Rate-limiting of neighbor reachability hints"}},{"before":"885b621cb39d77372274602814fb0a2f71523ec5","after":"c5ee6e4cc42726fe1ed4aa45963b4d5d6d771a62","ref":"refs/heads/pr/nd-reachability-hint","pushedAt":"2024-01-30T07:58:52.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"LuDuda","name":"Łukasz Duda","path":"/LuDuda","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5144764?s=80&v=4"},"commit":{"message":"net: ipv6: nbr: Add IPv6 reachability confirmation API\n\nThis commit introduces a new IPv6 API for positive reachability\nconfirmation, as specified in RFC 4861, Section 7.3.1. This feature aims\nto enhance the effectiveness of the Neighbor Discovery mechanism, by\nenabling upper-layer protocols to signal that the connection makes a\n\"forward progress\".\n\nThe implementation within TCP serves as a reference. Compliance with\nRFC 4861, especially Appendix E.1, was ensured by focusing on reliable\nhandshake and acknowledgment of new data transmissions.\n\nThough initially integrated with TCP, the API is designed for broader\napplicability. For example, it might be used by some UDP-based protocols\nthat can indicate two-way communication progress.\n\nSigned-off-by: Łukasz Duda ","shortMessageHtmlLink":"net: ipv6: nbr: Add IPv6 reachability confirmation API"}},{"before":"5ada8b13ccf38a3886a7827d2cd35cdec79ab2c3","after":"885b621cb39d77372274602814fb0a2f71523ec5","ref":"refs/heads/pr/nd-reachability-hint","pushedAt":"2024-01-29T15:20:05.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"LuDuda","name":"Łukasz Duda","path":"/LuDuda","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5144764?s=80&v=4"},"commit":{"message":"net: ipv6: nbr: Add IPv6 reachability confirmation API\n\nThis commit introduces a new IPv6 API for positive reachability\nconfirmation, as specified in RFC 4861, Section 7.3.1. This feature aims\nto enhance the effectiveness of the Neighbor Discovery mechanism, by\nenabling upper-layer protocols to signal that the connection makes a\n\"forward progress\".\n\nThe implementation within TCP serves as a reference. Compliance with\nRFC 4861, especially Appendix E.1, was ensured by focusing on reliable\nhandshake and acknowledgment of new data transmissions.\n\nThough initially integrated with TCP, the API is designed for broader\napplicability. For example, it might be used by some UDP-based protocols\nthat can indicate two-way communication progress.\n\nSigned-off-by: Łukasz Duda ","shortMessageHtmlLink":"net: ipv6: nbr: Add IPv6 reachability confirmation API"}},{"before":"1553e3ed42a8d407411ce08e8010f1cdcaec98d5","after":"5ada8b13ccf38a3886a7827d2cd35cdec79ab2c3","ref":"refs/heads/pr/nd-reachability-hint","pushedAt":"2024-01-29T14:02:09.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"LuDuda","name":"Łukasz Duda","path":"/LuDuda","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5144764?s=80&v=4"},"commit":{"message":"net: ipv6: nbr: Add IPv6 reachability confirmation API\n\nThis commit introduces a new IPv6 API for positive reachability\nconfirmation, as specified in RFC 4861, Section 7.3.1. This feature aims\nto enhance the effectiveness of the Neighbor Discovery mechanism, by\nenabling upper-layer protocols to signal that the connection makes a\n\"forward progress\".\n\nThe implementation within TCP serves as a reference, and the feature is\nkept disabled by default to minimize impact on the existing network\nstack. Compliance with RFC 4861, especially Appendix E.1, was ensured by\nfocusing on reliable handshake and acknowledgment of new data\ntransmissions.\n\nThough initially integrated with TCP, the API is designed for broader\napplicability. For example, it might be used by some UDP-based protocols\nthat can indicate two-way communication progress.\n\nSigned-off-by: Łukasz Duda ","shortMessageHtmlLink":"net: ipv6: nbr: Add IPv6 reachability confirmation API"}},{"before":"916bd788097deb41b7b3ea031d55cc56ebd1d666","after":"1553e3ed42a8d407411ce08e8010f1cdcaec98d5","ref":"refs/heads/pr/nd-reachability-hint","pushedAt":"2024-01-29T11:48:31.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"LuDuda","name":"Łukasz Duda","path":"/LuDuda","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5144764?s=80&v=4"},"commit":{"message":"net: ipv6: nbr: Add IPv6 reachability confirmation API\n\nThis commit introduces a new IPv6 API for positive reachability\nconfirmation, as specified in RFC 4861, Section 7.3.1. This feature aims\nto enhance the effectiveness of the Neighbor Discovery mechanism, by\nenabling upper-layer protocols to signal that the connection makes a\n\"forward progress\".\n\nThe implementation within TCP serves as a reference, and the feature is\nkept disabled by default to minimize impact on the existing network\nstack. Compliance with RFC 4861, especially Appendix E.1, was ensured by\nfocusing on reliable handshake and acknowledgment of new data\ntransmissions.\n\nThough initially integrated with TCP, the API is designed for broader\napplicability. For example, it might be used by some UDP-based protocols\nthat can indicate two-way communication progress.\n\nSigned-off-by: Łukasz Duda ","shortMessageHtmlLink":"net: ipv6: nbr: Add IPv6 reachability confirmation API"}},{"before":"d41ab0bb10e3b4b70acc6a5e6fb5b01155761cdf","after":"916bd788097deb41b7b3ea031d55cc56ebd1d666","ref":"refs/heads/pr/nd-reachability-hint","pushedAt":"2024-01-29T11:46:39.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"LuDuda","name":"Łukasz Duda","path":"/LuDuda","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5144764?s=80&v=4"},"commit":{"message":"net: ipv6: nbr: Add IPv6 reachability confirmation API\n\nThis commit introduces a new IPv6 API for positive reachability\nconfirmation, as specificed in RFC 4861, Section 7.3.1. This feature\naims to enhance effectiveness of Neighbor Discovery mechanism, by\nenabling upper-layer protocols to signal that connection makes a\n\"forward progress\".\n\nThe implementation within TCP serves as a reference, and the feature is\nkept disabled by default to minimize impact on the existing network\nstack. Compliance with RFC 4861, especially Appendix E.1, was ensured by\nfocusing on reliable handshake and acknowledgment of new data\ntransmissions.\n\nThough initially integrated with TCP, the API is designed for broader\napplicability. For example, it might be used by some UDP-based protocols\nthat are able to indicate two-way communication progress.\n\nSigned-off-by: Łukasz Duda ","shortMessageHtmlLink":"net: ipv6: nbr: Add IPv6 reachability confirmation API"}},{"before":"d7af25c821b9dafa36aba8ea3e55799be45812dd","after":"d41ab0bb10e3b4b70acc6a5e6fb5b01155761cdf","ref":"refs/heads/pr/nd-reachability-hint","pushedAt":"2024-01-29T11:45:22.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"LuDuda","name":"Łukasz Duda","path":"/LuDuda","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5144764?s=80&v=4"},"commit":{"message":"net: ipv6: nbr: Add IPv6 reachability confirmation API\n\nThis commit introduces a new IPv6 API for positive reachability\nconfirmation, as specificed in RFC 4861, Section 7.3.1. This feature\naims to enhance effectiveness of Neighbor Discovery mechanism, by\nenabling upper-layer protocols to signal that connection makes a\n\"forward progress\".\n\nThe implementation within TCP serves as a reference, and the feature is\nkept disabled by default to minimize impact on the existing network\nstack. Compliance with RFC 4861, especially Appendix E.1, was ensured by\nfocusing on reliable handshake and acknowledgment of new data\ntransmissions.\n\nThough initially integrated with TCP, the API is designed for broader\napplicability. For example, it might be used by some UDP-based protocols\nthat are able to indicate two-way communication progress.\n\nSigned-off-by: Łukasz Duda ","shortMessageHtmlLink":"net: ipv6: nbr: Add IPv6 reachability confirmation API"}},{"before":"88f0288250f878cef834238cf13d138834af2c09","after":"d7af25c821b9dafa36aba8ea3e55799be45812dd","ref":"refs/heads/pr/nd-reachability-hint","pushedAt":"2024-01-28T17:47:33.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"LuDuda","name":"Łukasz Duda","path":"/LuDuda","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5144764?s=80&v=4"},"commit":{"message":"net: ipv6: nbr: Add IPv6 reachability confirmation API\n\nThis commit introduces a new IPv6 API for positive reachability\nconfirmation, as specificed in RFC 4861, Section 7.3.1. This feature\naims to enhance effectiveness of Neighbor Discovery mechanism, by\nenabling upper-layer protocols to signal that connection makes a\n\"forward progress\".\n\nThe implementation within TCP serves as a reference, and the feature is\nkept disabled by default to minimize impact on the existing network\nstack. Compliance with RFC 4861, especially Appendix E.1, was ensured by\nfocusing on reliable handshake and acknowledgment of new data\ntransmissions.\n\nThough initially integrated with TCP, the API is designed for broader\napplicability. For example, it might be used by some UDP-based protocols\nthat are able to indicate two-way communication progress.\n\nSigned-off-by: Łukasz Duda ","shortMessageHtmlLink":"net: ipv6: nbr: Add IPv6 reachability confirmation API"}},{"before":"8ee3f45a25c9814440cdf03bfce2d9a8e897cdba","after":"88f0288250f878cef834238cf13d138834af2c09","ref":"refs/heads/pr/nd-reachability-hint","pushedAt":"2024-01-28T16:22:31.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"LuDuda","name":"Łukasz Duda","path":"/LuDuda","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5144764?s=80&v=4"},"commit":{"message":"net: ipv6: nbr: Add IPv6 reachability confirmation API\n\nThis commit introduces a new IPv6 API for positive reachability\nconfirmation, as specificed in RFC 4861, Section 7.3.1. This feature\naims to enhance effectiveness of Neighbor Discovery mechanism, by\nenabling upper-layer protocols to signal that connection makes a\n\"forward progress\".\n\nThe implementation within TCP serves as a reference, and the feature is\nkept disabled by default to minimize impact on the existing network\nstack. Compliance with RFC 4861, especially Appendix E.1, was ensured by\nfocusing on reliable handshake and acknowledgment of new data\ntransmissions.\n\nThough initially integrated with TCP, the API is designed for broader\napplicability. For example, it might be used by some UDP-based protocols\nthat are able to indicate two-way communication progress.\n\nSigned-off-by: Łukasz Duda ","shortMessageHtmlLink":"net: ipv6: nbr: Add IPv6 reachability confirmation API"}},{"before":"14f908352c801ca2e916caca3bb987f2c10170d7","after":"8ee3f45a25c9814440cdf03bfce2d9a8e897cdba","ref":"refs/heads/pr/nd-reachability-hint","pushedAt":"2024-01-28T16:21:46.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"LuDuda","name":"Łukasz Duda","path":"/LuDuda","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5144764?s=80&v=4"},"commit":{"message":"net: ipv6: nbr: Add IPv6 reachability confirmation API\n\nThis commit introduces a new IPv6 API for positive reachability\nconfirmation, as specificed in RFC 4861, Section 7.3.1. This feature\naims to enhance effectiveness of Neighbor Discovery mechanism, by\nenabling upper-layer protocols to signal that connection makes a\n\"forward progress\".\n\nThe implementation within TCP serves as a reference, and the feature is\nkept disabled by default to minimize impact on the existing network\nstack. Compliance with RFC 4861, especially Appendix E.1, was ensured by\nfocusing on reliable handshake and acknowledgment of new data\ntransmissions.\n\nThough initially integrated with TCP, the API is designed for broader\napplicability. For example, it might be used by some UDP-based protocols\nthat are able to indicate two-way communication progress.\n\nSigned-off-by: Łukasz Duda ","shortMessageHtmlLink":"net: ipv6: nbr: Add IPv6 reachability confirmation API"}},{"before":null,"after":"14f908352c801ca2e916caca3bb987f2c10170d7","ref":"refs/heads/pr/nd-reachability-hint","pushedAt":"2024-01-28T16:13:13.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"LuDuda","name":"Łukasz Duda","path":"/LuDuda","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5144764?s=80&v=4"},"commit":{"message":"net: ipv6: nbr: Add IPv6 reachability confirmation API\n\nThis commit introduces a new IPv6 API for positive reachability\nconfirmation, as specificed in RFC 4861, Section 7.3.1. This feature\naims to enhance effectiveness of Neighbor Discovery mechanism, by\nenabling upper-layer protocols to signal that connection makes a\n\"forward progress\".\n\nThe implementation within TCP serves as a reference, and the feature is\nkept disabled by default to minimize impact on the existing network\nstack. Compliance with RFC 4861, especially Appendix E.1, was ensured by\nfocusing on reliable handshake and acknowledgment of new data\ntransmissions.\n\nThough initially integrated with TCP, the API is designed for broader\napplicability. For example, it might be used by some UDP-based protocols\nthat are able to indicate two-way communication progress.\n\nSigned-off-by: Łukasz Duda ","shortMessageHtmlLink":"net: ipv6: nbr: Add IPv6 reachability confirmation API"}},{"before":"059205291c00f30c9acdb5110016c8cbec190029","after":"eac720fefe15a6414250c0d368cd4c04a4333a7c","ref":"refs/heads/pr/csl-timeout-zephyr","pushedAt":"2023-05-09T20:52:57.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"LuDuda","name":"Łukasz Duda","path":"/LuDuda","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5144764?s=80&v=4"},"commit":{"message":"net: openthread: allow to configure OPENTHREAD_CSL_TIMEOUT\n\nAdded the possibility to set the default OpenThread CSL timeout using\nKconfig.\n\nSigned-off-by: Lukasz Duda ","shortMessageHtmlLink":"net: openthread: allow to configure OPENTHREAD_CSL_TIMEOUT"}},{"before":"a8a8f5ca5eb60434dc55c44620ff060567b61555","after":"059205291c00f30c9acdb5110016c8cbec190029","ref":"refs/heads/pr/csl-timeout-zephyr","pushedAt":"2023-05-09T20:51:29.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"LuDuda","name":"Łukasz Duda","path":"/LuDuda","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5144764?s=80&v=4"},"commit":{"message":"[nrf fromlist] net: openthread: configure OPENTHREAD_CSL_TIMEOUT\n\nAdded the possibility to set the default OpenThread CSL timeout using\nKconfig.\n\nUpstream PR: https://github.com/zephyrproject-rtos/zephyr/pull/57716\n\nSigned-off-by: Lukasz Duda ","shortMessageHtmlLink":"[nrf fromlist] net: openthread: configure OPENTHREAD_CSL_TIMEOUT"}},{"before":null,"after":"a8a8f5ca5eb60434dc55c44620ff060567b61555","ref":"refs/heads/pr/csl-timeout-zephyr","pushedAt":"2023-05-09T20:44:40.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"LuDuda","name":"Łukasz Duda","path":"/LuDuda","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5144764?s=80&v=4"},"commit":{"message":"net: openthread: allow to configure OPENTHREAD_CSL_TIMEOUT\n\nAdded the possibility to set the default OpenThread CSL timeout using\nKconfig.\n\nSigned-off-by: Lukasz Duda ","shortMessageHtmlLink":"net: openthread: allow to configure OPENTHREAD_CSL_TIMEOUT"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"Y3Vyc29yOnYyOpK7MjAyNC0wOC0xOFQxOTozNjo1My4wMDAwMDBazwAAAASdbgr-","startCursor":"Y3Vyc29yOnYyOpK7MjAyNC0wOC0xOFQxOTozNjo1My4wMDAwMDBazwAAAASdbgr-","endCursor":"Y3Vyc29yOnYyOpK7MjAyMy0wNS0wOVQyMDo0NDo0MC4wMDAwMDBazwAAAAMpYvDE"}},"title":"Activity · LuDuda/zephyr"}