{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":45821540,"defaultBranch":"main","name":"openwrt","ownerLogin":"openwrt","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2015-11-09T07:13:55.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/2528830?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1714003230.0","currentOid":""},"activityList":{"items":[{"before":"918d81a3eac01be2309a54435e06f0a9d6c6f812","after":"ecb3859cc92d2e670847934c74255a4453915beb","ref":"refs/heads/master","pushedAt":"2024-05-02T20:09:25.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"openwrt-bot","name":null,"path":"/openwrt-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/99696057?s=80&v=4"},"commit":{"message":"ipq40xx: fritzrepeater-1200: fix MDIO and PHY probing\n\nAVM FRITZ!Repeater 1200 does not use QCA807x PHY at all and thus it\ndisables all of the individual PHY nodes, however this is not enough\nanymore since the conversion to PHY package.\n\nNow its now enough to disable the PHY-s in the package alone, but the PHY\npackage node itself must also be disabled.\n\nFixes: 1b931c33a28e (\"ipq40xx: adapt to new Upstream QCA807x PHY driver\")\nFixes: #15355\nLink: https://github.com/openwrt/openwrt/pull/15365\nSigned-off-by: Robert Marko ","shortMessageHtmlLink":"ipq40xx: fritzrepeater-1200: fix MDIO and PHY probing"}},{"before":"918d81a3eac01be2309a54435e06f0a9d6c6f812","after":"ecb3859cc92d2e670847934c74255a4453915beb","ref":"refs/heads/main","pushedAt":"2024-05-02T20:09:25.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"openwrt-bot","name":null,"path":"/openwrt-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/99696057?s=80&v=4"},"commit":{"message":"ipq40xx: fritzrepeater-1200: fix MDIO and PHY probing\n\nAVM FRITZ!Repeater 1200 does not use QCA807x PHY at all and thus it\ndisables all of the individual PHY nodes, however this is not enough\nanymore since the conversion to PHY package.\n\nNow its now enough to disable the PHY-s in the package alone, but the PHY\npackage node itself must also be disabled.\n\nFixes: 1b931c33a28e (\"ipq40xx: adapt to new Upstream QCA807x PHY driver\")\nFixes: #15355\nLink: https://github.com/openwrt/openwrt/pull/15365\nSigned-off-by: Robert Marko ","shortMessageHtmlLink":"ipq40xx: fritzrepeater-1200: fix MDIO and PHY probing"}},{"before":"219018185e52a49b6a676a3591fe28406bb1a062","after":"918d81a3eac01be2309a54435e06f0a9d6c6f812","ref":"refs/heads/master","pushedAt":"2024-05-02T13:59:15.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"openwrt-bot","name":null,"path":"/openwrt-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/99696057?s=80&v=4"},"commit":{"message":"mediatek: increase size of the sdcard image to 512 MiB\n\nIncreasing the size of the rootfs_data filesystem has become a ever\nrepeating discussion and seems to be the most important thing for\nusers of the MediaTek-based BananaPi boards.\n\nUsing the whole remaining size of a microSD or the eMMC for rootfs_data\ndoesn't make sense for many reasons, but neither does the current\ndefault of 104 MiB for the 'rootfs' partition size.\n\nIncrease the 'rootfs' partition size to 448 MiB which will result in\nthe sdcard image being exactly 512 MiB. Finding a microSD card smaller\nthan 512 MiB and still working could anyway be difficult in 2024.\n\nThat will allow users to install even bloatware written in Go or other\nspace-hungry languages while still leaving most of the space unallocated\nfor additional partitions or volumes to be used for persistent user\ndata.\n\nSigned-off-by: Daniel Golle ","shortMessageHtmlLink":"mediatek: increase size of the sdcard image to 512 MiB"}},{"before":"219018185e52a49b6a676a3591fe28406bb1a062","after":"918d81a3eac01be2309a54435e06f0a9d6c6f812","ref":"refs/heads/main","pushedAt":"2024-05-02T13:59:15.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"openwrt-bot","name":null,"path":"/openwrt-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/99696057?s=80&v=4"},"commit":{"message":"mediatek: increase size of the sdcard image to 512 MiB\n\nIncreasing the size of the rootfs_data filesystem has become a ever\nrepeating discussion and seems to be the most important thing for\nusers of the MediaTek-based BananaPi boards.\n\nUsing the whole remaining size of a microSD or the eMMC for rootfs_data\ndoesn't make sense for many reasons, but neither does the current\ndefault of 104 MiB for the 'rootfs' partition size.\n\nIncrease the 'rootfs' partition size to 448 MiB which will result in\nthe sdcard image being exactly 512 MiB. Finding a microSD card smaller\nthan 512 MiB and still working could anyway be difficult in 2024.\n\nThat will allow users to install even bloatware written in Go or other\nspace-hungry languages while still leaving most of the space unallocated\nfor additional partitions or volumes to be used for persistent user\ndata.\n\nSigned-off-by: Daniel Golle ","shortMessageHtmlLink":"mediatek: increase size of the sdcard image to 512 MiB"}},{"before":"6a05d849e1f8e9b3a879cdf4113afd88ebc0678a","after":"219018185e52a49b6a676a3591fe28406bb1a062","ref":"refs/heads/master","pushedAt":"2024-05-01T19:33:21.000Z","pushType":"push","commitsCount":4,"pusher":{"login":"openwrt-bot","name":null,"path":"/openwrt-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/99696057?s=80&v=4"},"commit":{"message":"bmips: Build U-Boot into the XG6846 target\n\nIt appears that the CFE boot loader found in the XG6846\ncannot load kernels over a certain size, and the old\nrelocate hack is not working.\n\nWhat to do? We can build a small U-Boot into the image,\nmake CFE boot that, place the kernel immediately after\nU-Boot, and use U-Boot to boot the system instead.\n\nThe compiled u-boot.bin becomes around ~300KB and with\nLZMA compression it will swiftly fit into 128KB, so\nwe use two 64KB erase blocks right after the CFE to\nstore an imagetag:ed U-Boot.\n\nReviewed-by: Paul Donald \nSigned-off-by: Linus Walleij ","shortMessageHtmlLink":"bmips: Build U-Boot into the XG6846 target"}},{"before":"6a05d849e1f8e9b3a879cdf4113afd88ebc0678a","after":"219018185e52a49b6a676a3591fe28406bb1a062","ref":"refs/heads/main","pushedAt":"2024-05-01T19:33:21.000Z","pushType":"push","commitsCount":4,"pusher":{"login":"openwrt-bot","name":null,"path":"/openwrt-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/99696057?s=80&v=4"},"commit":{"message":"bmips: Build U-Boot into the XG6846 target\n\nIt appears that the CFE boot loader found in the XG6846\ncannot load kernels over a certain size, and the old\nrelocate hack is not working.\n\nWhat to do? We can build a small U-Boot into the image,\nmake CFE boot that, place the kernel immediately after\nU-Boot, and use U-Boot to boot the system instead.\n\nThe compiled u-boot.bin becomes around ~300KB and with\nLZMA compression it will swiftly fit into 128KB, so\nwe use two 64KB erase blocks right after the CFE to\nstore an imagetag:ed U-Boot.\n\nReviewed-by: Paul Donald \nSigned-off-by: Linus Walleij ","shortMessageHtmlLink":"bmips: Build U-Boot into the XG6846 target"}},{"before":"5acc4f919c28ee8ea20c98856e1e824168cf2270","after":"6a05d849e1f8e9b3a879cdf4113afd88ebc0678a","ref":"refs/heads/master","pushedAt":"2024-05-01T18:23:57.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"openwrt-bot","name":null,"path":"/openwrt-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/99696057?s=80&v=4"},"commit":{"message":"bcm27xx: correct cmdline.txt consoles for procd\n\nCommit [ca8c30208d5e][1] updates procd to handle muliple \"console=\" on the\nkernel command line. This affects Raspberry Pi builds because cmdline.txt\nspecifies a UART console and a virtual console on HDMI, in that order.\n\nWhen procd finds multiple consoles on the command line, it attempts to\nopen /dev/console. Linux uses the [last console][2] for /dev/console, so\nprocd opens the virtual console on Raspberry Pi. This completely disables\nthe UART console and causes [strange behavior][3] on the virtual console.\nPrior to ca8c30208d5e, procd would always open the first console, which is\nthe UART console.\n\nThe simplest fix without reverting ca8c30208d5e is to swap the order of\nconsole options in cmdline.txt. By putting the UART console last, procd\nhandles the serial console correctly as before.\n\n[1]: https://git.openwrt.org/?p=project/procd.git;a=commit;h=ca8c30208d5e1aaa2c0e3f732c4c9944735e9850\n[2]: https://www.kernel.org/doc/html/latest/admin-guide/serial-console.html\n[3]: https://forum.openwrt.org/t/rasberry-pi-4-model-b-keyboards-gone-wild/195594\n\nSigned-off-by: Elbert Mai ","shortMessageHtmlLink":"bcm27xx: correct cmdline.txt consoles for procd"}},{"before":"5acc4f919c28ee8ea20c98856e1e824168cf2270","after":"6a05d849e1f8e9b3a879cdf4113afd88ebc0678a","ref":"refs/heads/main","pushedAt":"2024-05-01T18:23:57.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"openwrt-bot","name":null,"path":"/openwrt-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/99696057?s=80&v=4"},"commit":{"message":"bcm27xx: correct cmdline.txt consoles for procd\n\nCommit [ca8c30208d5e][1] updates procd to handle muliple \"console=\" on the\nkernel command line. This affects Raspberry Pi builds because cmdline.txt\nspecifies a UART console and a virtual console on HDMI, in that order.\n\nWhen procd finds multiple consoles on the command line, it attempts to\nopen /dev/console. Linux uses the [last console][2] for /dev/console, so\nprocd opens the virtual console on Raspberry Pi. This completely disables\nthe UART console and causes [strange behavior][3] on the virtual console.\nPrior to ca8c30208d5e, procd would always open the first console, which is\nthe UART console.\n\nThe simplest fix without reverting ca8c30208d5e is to swap the order of\nconsole options in cmdline.txt. By putting the UART console last, procd\nhandles the serial console correctly as before.\n\n[1]: https://git.openwrt.org/?p=project/procd.git;a=commit;h=ca8c30208d5e1aaa2c0e3f732c4c9944735e9850\n[2]: https://www.kernel.org/doc/html/latest/admin-guide/serial-console.html\n[3]: https://forum.openwrt.org/t/rasberry-pi-4-model-b-keyboards-gone-wild/195594\n\nSigned-off-by: Elbert Mai ","shortMessageHtmlLink":"bcm27xx: correct cmdline.txt consoles for procd"}},{"before":"b6f1e2e5b08eccf23b28c80690d14a3ac6cd08e2","after":"5acc4f919c28ee8ea20c98856e1e824168cf2270","ref":"refs/heads/master","pushedAt":"2024-05-01T17:12:00.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"openwrt-bot","name":null,"path":"/openwrt-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/99696057?s=80&v=4"},"commit":{"message":"xdp-tools: fix compilation wrongly using host header\n\nCurrently it's needed to have gcc-multilib on the host to correctly\ncompile xdp-tools. This is wrong and means that we are using host header\nto compile a tool.\n\nBy some searching in how the makefile works it was discovered that\nBPF_CFLAGS were not used and required to be appended to config.mk\n\nOnly one single header was added but we should include each BPF_CFLAGS\nfrom bpf.mk. To make this some patching to bpf-header were required and\nsome patches to xdp-tools were required.\nAlso it's needed to pass the correct target to BPF_CFLAGS.\n\nWith the following changes xdp-tools can correctly compile with each\nheader from bpf-headers and should not use any host header.\n\nCo-Developed-by: Andre Heider \nSigned-off-by: Andre Heider \nLink: https://github.com/openwrt/openwrt/pull/11825\nSigned-off-by: Christian Marangi ","shortMessageHtmlLink":"xdp-tools: fix compilation wrongly using host header"}},{"before":"b6f1e2e5b08eccf23b28c80690d14a3ac6cd08e2","after":"5acc4f919c28ee8ea20c98856e1e824168cf2270","ref":"refs/heads/main","pushedAt":"2024-05-01T17:12:00.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"openwrt-bot","name":null,"path":"/openwrt-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/99696057?s=80&v=4"},"commit":{"message":"xdp-tools: fix compilation wrongly using host header\n\nCurrently it's needed to have gcc-multilib on the host to correctly\ncompile xdp-tools. This is wrong and means that we are using host header\nto compile a tool.\n\nBy some searching in how the makefile works it was discovered that\nBPF_CFLAGS were not used and required to be appended to config.mk\n\nOnly one single header was added but we should include each BPF_CFLAGS\nfrom bpf.mk. To make this some patching to bpf-header were required and\nsome patches to xdp-tools were required.\nAlso it's needed to pass the correct target to BPF_CFLAGS.\n\nWith the following changes xdp-tools can correctly compile with each\nheader from bpf-headers and should not use any host header.\n\nCo-Developed-by: Andre Heider \nSigned-off-by: Andre Heider \nLink: https://github.com/openwrt/openwrt/pull/11825\nSigned-off-by: Christian Marangi ","shortMessageHtmlLink":"xdp-tools: fix compilation wrongly using host header"}},{"before":"a8bfdf2ed4d930ca5a31b5c4bc7061ad5ef11ba3","after":"b6f1e2e5b08eccf23b28c80690d14a3ac6cd08e2","ref":"refs/heads/master","pushedAt":"2024-05-01T17:01:17.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"openwrt-bot","name":null,"path":"/openwrt-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/99696057?s=80&v=4"},"commit":{"message":"ucode: fix ubus defer when running from within eloop (integrated with uloop)\n\nSigned-off-by: Felix Fietkau ","shortMessageHtmlLink":"ucode: fix ubus defer when running from within eloop (integrated with…"}},{"before":"a8bfdf2ed4d930ca5a31b5c4bc7061ad5ef11ba3","after":"b6f1e2e5b08eccf23b28c80690d14a3ac6cd08e2","ref":"refs/heads/main","pushedAt":"2024-05-01T17:01:17.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"openwrt-bot","name":null,"path":"/openwrt-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/99696057?s=80&v=4"},"commit":{"message":"ucode: fix ubus defer when running from within eloop (integrated with uloop)\n\nSigned-off-by: Felix Fietkau ","shortMessageHtmlLink":"ucode: fix ubus defer when running from within eloop (integrated with…"}},{"before":"507f9439e7b930cfd8033dbfeaf3fe7df2e9dfd3","after":"eda76b336b6b6719434fd7cc314ba51fa18eda5c","ref":"refs/heads/openwrt-23.05","pushedAt":"2024-05-01T13:47:07.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"openwrt-bot","name":null,"path":"/openwrt-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/99696057?s=80&v=4"},"commit":{"message":"gengetopt: backport patch fixing support for c++17\n\nBackport patch fixing support for c++17 that got merged upstream in\ngengetopt.\n\nSigned-off-by: Christian Marangi \n(cherry picked from commit a8bfdf2ed4d930ca5a31b5c4bc7061ad5ef11ba3)","shortMessageHtmlLink":"gengetopt: backport patch fixing support for c++17"}},{"before":"3ea6125c501e3adc81227cc69fb9e28eec69f2b8","after":"a8bfdf2ed4d930ca5a31b5c4bc7061ad5ef11ba3","ref":"refs/heads/master","pushedAt":"2024-05-01T13:46:13.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"openwrt-bot","name":null,"path":"/openwrt-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/99696057?s=80&v=4"},"commit":{"message":"gengetopt: backport patch fixing support for c++17\n\nBackport patch fixing support for c++17 that got merged upstream in\ngengetopt.\n\nSigned-off-by: Christian Marangi ","shortMessageHtmlLink":"gengetopt: backport patch fixing support for c++17"}},{"before":"3ea6125c501e3adc81227cc69fb9e28eec69f2b8","after":"a8bfdf2ed4d930ca5a31b5c4bc7061ad5ef11ba3","ref":"refs/heads/main","pushedAt":"2024-05-01T13:46:13.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"openwrt-bot","name":null,"path":"/openwrt-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/99696057?s=80&v=4"},"commit":{"message":"gengetopt: backport patch fixing support for c++17\n\nBackport patch fixing support for c++17 that got merged upstream in\ngengetopt.\n\nSigned-off-by: Christian Marangi ","shortMessageHtmlLink":"gengetopt: backport patch fixing support for c++17"}},{"before":"d06bcbe5bffc9aea68c518ea672f4e799a6e9b26","after":"3ea6125c501e3adc81227cc69fb9e28eec69f2b8","ref":"refs/heads/master","pushedAt":"2024-05-01T12:51:59.000Z","pushType":"push","commitsCount":4,"pusher":{"login":"openwrt-bot","name":null,"path":"/openwrt-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/99696057?s=80&v=4"},"commit":{"message":"ramips: mt7621-dts: describe switch PHYs and adjust PHY muxing\n\nCurrently, the MT7530 DSA subdriver configures the MT7530 switch to provide\ndirect access to switch PHYs, meaning, the switch PHYs listen on the MDIO\nbus the switch listens on. The PHY muxing feature makes use of this.\n\nThis is problematic as the PHY may be attached before the switch is\ninitialised, in which case, the PHY will fail to be attached.\n\nSince commit 91374ba537bd (\"net: dsa: mt7530: support OF-based registration\nof switch MDIO bus\") on mainline Linux, we can describe the switch PHYs on\nthe MDIO bus of the switch on the device tree.\n\nWhen the PHY is described this way, the switch will be initialised first,\nthen the switch MDIO bus will be registered. Only after these steps, the\nPHY will be attached.\n\nDescribe the switch PHYs on mt7621.dtsi and remove defining the switch PHY\non the SoC's mdio bus node. When the PHY muxing is in use, the interrupts\nfor the muxed PHY won't work, therefore delete the \"interrupts\" property on\nthe devices where the PHY muxing feature is in use.\n\nSigned-off-by: Arınç ÜNAL ","shortMessageHtmlLink":"ramips: mt7621-dts: describe switch PHYs and adjust PHY muxing"}},{"before":"d06bcbe5bffc9aea68c518ea672f4e799a6e9b26","after":"3ea6125c501e3adc81227cc69fb9e28eec69f2b8","ref":"refs/heads/main","pushedAt":"2024-05-01T12:51:59.000Z","pushType":"push","commitsCount":4,"pusher":{"login":"openwrt-bot","name":null,"path":"/openwrt-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/99696057?s=80&v=4"},"commit":{"message":"ramips: mt7621-dts: describe switch PHYs and adjust PHY muxing\n\nCurrently, the MT7530 DSA subdriver configures the MT7530 switch to provide\ndirect access to switch PHYs, meaning, the switch PHYs listen on the MDIO\nbus the switch listens on. The PHY muxing feature makes use of this.\n\nThis is problematic as the PHY may be attached before the switch is\ninitialised, in which case, the PHY will fail to be attached.\n\nSince commit 91374ba537bd (\"net: dsa: mt7530: support OF-based registration\nof switch MDIO bus\") on mainline Linux, we can describe the switch PHYs on\nthe MDIO bus of the switch on the device tree.\n\nWhen the PHY is described this way, the switch will be initialised first,\nthen the switch MDIO bus will be registered. Only after these steps, the\nPHY will be attached.\n\nDescribe the switch PHYs on mt7621.dtsi and remove defining the switch PHY\non the SoC's mdio bus node. When the PHY muxing is in use, the interrupts\nfor the muxed PHY won't work, therefore delete the \"interrupts\" property on\nthe devices where the PHY muxing feature is in use.\n\nSigned-off-by: Arınç ÜNAL ","shortMessageHtmlLink":"ramips: mt7621-dts: describe switch PHYs and adjust PHY muxing"}},{"before":"9e86e0b33bfa1a81cfc92647def72f151da2e5b7","after":"d06bcbe5bffc9aea68c518ea672f4e799a6e9b26","ref":"refs/heads/master","pushedAt":"2024-05-01T10:14:22.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"openwrt-bot","name":null,"path":"/openwrt-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/99696057?s=80&v=4"},"commit":{"message":"zynq: 5.15: remove files\n\nRemove files related to the old 5.15 kernel version as they are no\nlonger required.\n\nSigned-off-by: Nick Hainke ","shortMessageHtmlLink":"zynq: 5.15: remove files"}},{"before":"9e86e0b33bfa1a81cfc92647def72f151da2e5b7","after":"d06bcbe5bffc9aea68c518ea672f4e799a6e9b26","ref":"refs/heads/main","pushedAt":"2024-05-01T10:14:22.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"openwrt-bot","name":null,"path":"/openwrt-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/99696057?s=80&v=4"},"commit":{"message":"zynq: 5.15: remove files\n\nRemove files related to the old 5.15 kernel version as they are no\nlonger required.\n\nSigned-off-by: Nick Hainke ","shortMessageHtmlLink":"zynq: 5.15: remove files"}},{"before":"451b51f0dc02ae1a06cf2afb68294bfb0bb63606","after":"507f9439e7b930cfd8033dbfeaf3fe7df2e9dfd3","ref":"refs/heads/openwrt-23.05","pushedAt":"2024-04-30T21:48:37.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"openwrt-bot","name":null,"path":"/openwrt-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/99696057?s=80&v=4"},"commit":{"message":"lua: fix CVE-2014-5461\n\nPatch taken from Debian.\n\nRefresh patches\n\nSigned-off-by: Rosen Penev \n(cherry picked from commit 78b0106f7d5093641f68d37c041a5863eb9dd9a0)","shortMessageHtmlLink":"lua: fix CVE-2014-5461"}},{"before":"ed12436ee92ea29375dc0b4d592063636cc83ccc","after":"451b51f0dc02ae1a06cf2afb68294bfb0bb63606","ref":"refs/heads/openwrt-23.05","pushedAt":"2024-04-30T21:43:17.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"openwrt-bot","name":null,"path":"/openwrt-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/99696057?s=80&v=4"},"commit":{"message":"kernel: bump 5.15 to 5.15.155\n\nManual adapted the following patches:\n generic/hack-5.15/221-module_exports.patch\n bcm27xx/patches-5.15/950-0008-drm-vc4-hdmi-Use-a-mutex-to-prevent-concurrent-frame.patch\n octeontx/patches-5.15/0004-PCI-add-quirk-for-Gateworks-PLX-PEX860x-switch-with-.patch\n\nSigned-off-by: Hauke Mehrtens \n(cherry picked from commit 9693ed6a9edb2ec9c9aa5edfa816dda3897cdfc4)","shortMessageHtmlLink":"kernel: bump 5.15 to 5.15.155"}},{"before":"dcdcb9228be01e08ee6c1b7f5a7c60af53e07176","after":"9e86e0b33bfa1a81cfc92647def72f151da2e5b7","ref":"refs/heads/master","pushedAt":"2024-04-30T18:20:13.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"openwrt-bot","name":null,"path":"/openwrt-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/99696057?s=80&v=4"},"commit":{"message":"kernel: bump 6.1 to 6.1.89\n\nChangelogs:\nhttps://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.67\nhttps://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.68\nhttps://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.69\n\nUpstreamed patches:\ntarget/linux/generic/backport-6.1/740-v6.9-01-netfilter-flowtable-validate-pppoe-header.patch [1]\ntarget/linux/generic/backport-6.1/740-v6.9-02-netfilter-flowtable-incorrect-pppoe-tuple.patch [2]\ntarget/linux/generic/backport-6.1/790-48-STABLE-net-dsa-mt7530-trap-link-local-frames-regardless-of-.patch [3]\ntarget/linux/generic/backport-6.1/790-50-v6.10-net-dsa-mt7530-fix-mirroring-frames-received-on-loca.patch [4]\ntarget/linux/generic/backport-6.1/790-16-v6.4-net-dsa-mt7530-set-all-CPU-ports-in-MT7531_CPU_PMAP.patch [5]\ntarget/linux/generic/backport-6.1/790-46-v6.9-net-dsa-mt7530-fix-improper-frames-on-all-25MHz-and-.patch [6]\ntarget/linux/generic/backport-6.1/790-47-v6.10-net-dsa-mt7530-fix-enabling-EEE-on-MT7531-switch-on-.patch [7]\ntarget/linux/mediatek/patches-6.1/220-v6.3-clk-mediatek-clk-gate-Propagate-struct-device-with-m.patch [8]\ntarget/linux/mediatek/patches-6.1/222-v6.3-clk-mediatek-clk-mtk-Propagate-struct-device-for-com.patch [9]\ntarget/linux/mediatek/patches-6.1/223-v6.3-clk-mediatek-clk-mux-Propagate-struct-device-for-mtk.patch [10]\ntarget/linux/mediatek/patches-6.1/226-v6.3-clk-mediatek-clk-mtk-Extend-mtk_clk_simple_probe.patch [11]\n\nSymbol changes:\nMITIGATION_SPECTRE_BHI (new) [12]\nSPECTRE_BHI_{ON,OFF} (deprecated) [12]\n\nReferences:\n[1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.89&id=8bf7c76a2a207ca2b4cfda0a279192adf27678d7\n[2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.89&id=f1c3c61701a0b12f4906152c1626a5de580ea3d2\n[3] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.89&id=19643bf8c9b5bb5eea5163bf2f6a3eee6fb5b99b\n[4] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.89&id=e86c9db58eba290e858e2bb80efcde9e3973a5ef\n[5] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.89&id=013c787d231188a6408e2991150d3c9bf9a2aa0b\n[6] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.89&id=41a004ffba9b1fd8a5a7128ebd0dfa3ed39c3316\n[7] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.89&id=7d51db455ca03e5270cc585a75a674abd063fa6c\n[8] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.89&id=082b831488a41257b7ac7ffa1d80a0b60d98394d\n[9] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.89&id=6f5f72a684a2823f21efbfd20c7e4b528c44a781\n[10] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.89&id=a4fe8813a7868ba5867e42e60de7a2b8baac30ff\n[11] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.89&id=c1d87d56af063c87961511ee25f6b07a5676d27d\n[12] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.89&id=d844df110084ef8bd950a52194865f3f63b561ca\nSigned-off-by: Shiji Yang ","shortMessageHtmlLink":"kernel: bump 6.1 to 6.1.89"}},{"before":"dcdcb9228be01e08ee6c1b7f5a7c60af53e07176","after":"9e86e0b33bfa1a81cfc92647def72f151da2e5b7","ref":"refs/heads/main","pushedAt":"2024-04-30T18:20:13.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"openwrt-bot","name":null,"path":"/openwrt-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/99696057?s=80&v=4"},"commit":{"message":"kernel: bump 6.1 to 6.1.89\n\nChangelogs:\nhttps://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.67\nhttps://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.68\nhttps://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.69\n\nUpstreamed patches:\ntarget/linux/generic/backport-6.1/740-v6.9-01-netfilter-flowtable-validate-pppoe-header.patch [1]\ntarget/linux/generic/backport-6.1/740-v6.9-02-netfilter-flowtable-incorrect-pppoe-tuple.patch [2]\ntarget/linux/generic/backport-6.1/790-48-STABLE-net-dsa-mt7530-trap-link-local-frames-regardless-of-.patch [3]\ntarget/linux/generic/backport-6.1/790-50-v6.10-net-dsa-mt7530-fix-mirroring-frames-received-on-loca.patch [4]\ntarget/linux/generic/backport-6.1/790-16-v6.4-net-dsa-mt7530-set-all-CPU-ports-in-MT7531_CPU_PMAP.patch [5]\ntarget/linux/generic/backport-6.1/790-46-v6.9-net-dsa-mt7530-fix-improper-frames-on-all-25MHz-and-.patch [6]\ntarget/linux/generic/backport-6.1/790-47-v6.10-net-dsa-mt7530-fix-enabling-EEE-on-MT7531-switch-on-.patch [7]\ntarget/linux/mediatek/patches-6.1/220-v6.3-clk-mediatek-clk-gate-Propagate-struct-device-with-m.patch [8]\ntarget/linux/mediatek/patches-6.1/222-v6.3-clk-mediatek-clk-mtk-Propagate-struct-device-for-com.patch [9]\ntarget/linux/mediatek/patches-6.1/223-v6.3-clk-mediatek-clk-mux-Propagate-struct-device-for-mtk.patch [10]\ntarget/linux/mediatek/patches-6.1/226-v6.3-clk-mediatek-clk-mtk-Extend-mtk_clk_simple_probe.patch [11]\n\nSymbol changes:\nMITIGATION_SPECTRE_BHI (new) [12]\nSPECTRE_BHI_{ON,OFF} (deprecated) [12]\n\nReferences:\n[1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.89&id=8bf7c76a2a207ca2b4cfda0a279192adf27678d7\n[2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.89&id=f1c3c61701a0b12f4906152c1626a5de580ea3d2\n[3] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.89&id=19643bf8c9b5bb5eea5163bf2f6a3eee6fb5b99b\n[4] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.89&id=e86c9db58eba290e858e2bb80efcde9e3973a5ef\n[5] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.89&id=013c787d231188a6408e2991150d3c9bf9a2aa0b\n[6] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.89&id=41a004ffba9b1fd8a5a7128ebd0dfa3ed39c3316\n[7] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.89&id=7d51db455ca03e5270cc585a75a674abd063fa6c\n[8] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.89&id=082b831488a41257b7ac7ffa1d80a0b60d98394d\n[9] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.89&id=6f5f72a684a2823f21efbfd20c7e4b528c44a781\n[10] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.89&id=a4fe8813a7868ba5867e42e60de7a2b8baac30ff\n[11] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.89&id=c1d87d56af063c87961511ee25f6b07a5676d27d\n[12] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.89&id=d844df110084ef8bd950a52194865f3f63b561ca\nSigned-off-by: Shiji Yang ","shortMessageHtmlLink":"kernel: bump 6.1 to 6.1.89"}},{"before":"be37ab6e51b7526d386fce035b6d668d64598248","after":"dcdcb9228be01e08ee6c1b7f5a7c60af53e07176","ref":"refs/heads/master","pushedAt":"2024-04-30T17:35:24.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"openwrt-bot","name":null,"path":"/openwrt-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/99696057?s=80&v=4"},"commit":{"message":"generic: MIPS64: fix detect_memory_region() compilation error\n\n1. Enable this feature only for 32-bit CPUs as MIPS64 can not\n access the full range unmapped uncached memory.\n\n2. Backport this fix to the 6.1 old LTS kernel.\n\nSigned-off-by: Shiji Yang ","shortMessageHtmlLink":"generic: MIPS64: fix detect_memory_region() compilation error"}},{"before":"be37ab6e51b7526d386fce035b6d668d64598248","after":"dcdcb9228be01e08ee6c1b7f5a7c60af53e07176","ref":"refs/heads/main","pushedAt":"2024-04-30T17:35:24.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"openwrt-bot","name":null,"path":"/openwrt-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/99696057?s=80&v=4"},"commit":{"message":"generic: MIPS64: fix detect_memory_region() compilation error\n\n1. Enable this feature only for 32-bit CPUs as MIPS64 can not\n access the full range unmapped uncached memory.\n\n2. Backport this fix to the 6.1 old LTS kernel.\n\nSigned-off-by: Shiji Yang ","shortMessageHtmlLink":"generic: MIPS64: fix detect_memory_region() compilation error"}},{"before":"00ff73ec6e815d9e82ef9164d23d445a2346579e","after":"be37ab6e51b7526d386fce035b6d668d64598248","ref":"refs/heads/master","pushedAt":"2024-04-30T11:51:22.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"openwrt-bot","name":null,"path":"/openwrt-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/99696057?s=80&v=4"},"commit":{"message":"qualcommax: ipq807x: uboot-envtools: yuncore ax880\n\nThere was no config in the uboot-envtools package, so there is no\ngenerated /etc/fw_env.config for the fw_printenv and fw_setenv utils.\nSince uboot-envtools 2024.01, there is a way to make these utils work\nwithout /etc/fw_env.config if the DT has an env partition with the prop.:\n\ncompatible = \"u-boot,env\";\n\nSo, this commit adds the prop. above to the appsblenv:0 partition\nin the yuncore ax880 DTS file.\n\nSigned-off-by: Isaev Ruslan \nLink: https://github.com/openwrt/openwrt/pull/15305\nSigned-off-by: Robert Marko ","shortMessageHtmlLink":"qualcommax: ipq807x: uboot-envtools: yuncore ax880"}},{"before":"00ff73ec6e815d9e82ef9164d23d445a2346579e","after":"be37ab6e51b7526d386fce035b6d668d64598248","ref":"refs/heads/main","pushedAt":"2024-04-30T11:51:22.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"openwrt-bot","name":null,"path":"/openwrt-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/99696057?s=80&v=4"},"commit":{"message":"qualcommax: ipq807x: uboot-envtools: yuncore ax880\n\nThere was no config in the uboot-envtools package, so there is no\ngenerated /etc/fw_env.config for the fw_printenv and fw_setenv utils.\nSince uboot-envtools 2024.01, there is a way to make these utils work\nwithout /etc/fw_env.config if the DT has an env partition with the prop.:\n\ncompatible = \"u-boot,env\";\n\nSo, this commit adds the prop. above to the appsblenv:0 partition\nin the yuncore ax880 DTS file.\n\nSigned-off-by: Isaev Ruslan \nLink: https://github.com/openwrt/openwrt/pull/15305\nSigned-off-by: Robert Marko ","shortMessageHtmlLink":"qualcommax: ipq807x: uboot-envtools: yuncore ax880"}},{"before":"47da1786e9554ee68e32287c747fd88bee539d53","after":"00ff73ec6e815d9e82ef9164d23d445a2346579e","ref":"refs/heads/master","pushedAt":"2024-04-30T11:38:06.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"openwrt-bot","name":null,"path":"/openwrt-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/99696057?s=80&v=4"},"commit":{"message":"tools/elfutils: remove dirname\n\nIn the 0.191 update dirname was used instead of to fix the\npoisoned basename error:\n/usr/include/libgen.h:35:9: error: attempt to use poisoned \"basename\"\n 35 | #define basename __xpg_basename\n\nHowever, doing this has lead to libelf.a pulling in xmalloc, xstrdup and\nfriends and statically linking them thus leading to a symbol name conflict\nwith FRR host build and anything else that links against libelf and uses\nxmalloc and friends.\n\nWell, it turns out that upstream has added a helper[1] for basename so it\ncan compile with musl 1.2.5 which dropped the basename declaration, but it\nalso means that we must NOT include and that poisoned error is\nintentional and added to prevent duplicate basename definitions.\nThis also means that for macOS we dont need to do any additional header\ninclusions as the new helper takes care of basename.\n\nSo, to fix the symbol conflict we can simply drop the inclusion\nand build from elfutils.\n\nTested on Fedora 40 as well as macOS 14.4.1.\n\n[1] https://sourceware.org/git/?p=elfutils.git;a=commit;h=a2194f6b305bf0d0b9dd49dccd0a5c21994c8eea\n\nFixes: #24030\nFixes: b6f025b42429 (\"tools/elfutils: update to 1.91\")\n\nLink: https://github.com/openwrt/openwrt/pull/15337\nSigned-off-by: Robert Marko ","shortMessageHtmlLink":"tools/elfutils: remove dirname"}},{"before":"47da1786e9554ee68e32287c747fd88bee539d53","after":"00ff73ec6e815d9e82ef9164d23d445a2346579e","ref":"refs/heads/main","pushedAt":"2024-04-30T11:38:06.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"openwrt-bot","name":null,"path":"/openwrt-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/99696057?s=80&v=4"},"commit":{"message":"tools/elfutils: remove dirname\n\nIn the 0.191 update dirname was used instead of to fix the\npoisoned basename error:\n/usr/include/libgen.h:35:9: error: attempt to use poisoned \"basename\"\n 35 | #define basename __xpg_basename\n\nHowever, doing this has lead to libelf.a pulling in xmalloc, xstrdup and\nfriends and statically linking them thus leading to a symbol name conflict\nwith FRR host build and anything else that links against libelf and uses\nxmalloc and friends.\n\nWell, it turns out that upstream has added a helper[1] for basename so it\ncan compile with musl 1.2.5 which dropped the basename declaration, but it\nalso means that we must NOT include and that poisoned error is\nintentional and added to prevent duplicate basename definitions.\nThis also means that for macOS we dont need to do any additional header\ninclusions as the new helper takes care of basename.\n\nSo, to fix the symbol conflict we can simply drop the inclusion\nand build from elfutils.\n\nTested on Fedora 40 as well as macOS 14.4.1.\n\n[1] https://sourceware.org/git/?p=elfutils.git;a=commit;h=a2194f6b305bf0d0b9dd49dccd0a5c21994c8eea\n\nFixes: #24030\nFixes: b6f025b42429 (\"tools/elfutils: update to 1.91\")\n\nLink: https://github.com/openwrt/openwrt/pull/15337\nSigned-off-by: Robert Marko ","shortMessageHtmlLink":"tools/elfutils: remove dirname"}},{"before":"2541ff391fc88d2fc378c4fa9374f8b1a3e4e9b9","after":"ed12436ee92ea29375dc0b4d592063636cc83ccc","ref":"refs/heads/openwrt-23.05","pushedAt":"2024-04-30T10:36:26.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"openwrt-bot","name":null,"path":"/openwrt-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/99696057?s=80&v=4"},"commit":{"message":"toolchain/gdb: backport patch for macOS to fix invalid range\n\nWith the recent macOS update to Ventura, it looks like gdb could not be\ncompiled with clang16 and newer version, because it fails with:\n./../gdbsupport/enum-flags.h:95:52: error: integer value -1 is outside the valid range of values [0, 15] for this enumeration type [-Wenum-constexpr-conversion]\n integer_for_size(T (-1) < T (0))>::type\n ^\n./../gdbsupport/enum-flags.h:95:52: error: integer value -1 is outside the valid range of values [0, 1] for this enumeration type [-Wenum-constexpr-conversion]\n./../gdbsupport/enum-flags.h:95:52: error: integer value -1 is outside the valid range of values [0, 3] for this enumeration type [-Wenum-constexpr-conversion]\n./../gdbsupport/enum-flags.h:95:52: error: integer value -1 is outside the valid range of values [0, 3] for this enumeration type [-Wenum-constexpr-conversion]\n4 errors generated.\n\n- Upstream bug:\nhttps://sourceware.org/bugzilla/show_bug.cgi?id=30423\n\n- Backported upstream commit:\nhttps://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=ae61525fcf456ab395d55c45492a106d1275873a\n\nFixes: https://github.com/openwrt/openwrt/issues/15314\n\nSigned-off-by: Josef Schlehofer \nLink: https://github.com/openwrt/openwrt/pull/15315\nSigned-off-by: Robert Marko ","shortMessageHtmlLink":"toolchain/gdb: backport patch for macOS to fix invalid range"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEQCz8kQA","startCursor":null,"endCursor":null}},"title":"Activity · openwrt/openwrt"}