aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/layerscape
Commit message (Collapse)AuthorAgeFilesLines
* kernel: bump 5.15 to 5.15.100John Audia2023-03-181-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Manually rebased: bcm27xx/patches-5.15/950-0421-Support-RPi-DPI-interface-in-mode6-for-18-bit-color.patch bcm27xx/patches-5.15/950-0706-media-i2c-imx219-Scale-the-pixel-clock-rate-for-the-.patch ramips/patches-5.15/810-uvc-add-iPassion-iP2970-support.patch Removed upstreamed: bcm27xx/patches-5.15/950-0707-drm-vc4-For-DPI-MEDIA_BUS_FMT_RGB565_1X16-is-mode-1-.patch[1] bcm27xx/patches-5.15/950-0596-drm-vc4-dpi-Add-option-for-inverting-pixel-clock-and.patch[2] ipq807x/0006-v5.16-arm64-dts-qcom-Fix-IPQ8074-PCIe-PHY-nodes.patch [3] ipq807x/0034-v6.1-arm64-dts-qcom-ipq8074-fix-PCIe-PHY-serdes-size.patch [4] ipq807x/0103-arm64-dts-qcom-ipq8074-fix-Gen2-PCIe-QMP-PHY.patch [5] ipq807x/0104-arm64-dts-qcom-ipq8074-fix-Gen3-PCIe-QMP-PHY.patch [6] ipq807x/0105-arm64-dts-qcom-ipq8074-correct-Gen2-PCIe-ranges.patch [7] ipq807x/0108-arm64-dts-qcom-ipq8074-fix-Gen3-PCIe-node.patch [8] ipq807x/0109-arm64-dts-qcom-ipq8074-correct-PCIe-QMP-PHY-output-c.patch [9] ipq807x/0132-arm64-dts-qcom-ipq8074-correct-USB3-QMP-PHY-s-clock-.patch [10] All other patches automatically rebased. 1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.15.99&id=d2991e6b30020e286f2dd9d3b4f43548c547caa6 2. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpu/drm/vc4/vc4_dpi.c?h=v5.15.100&id=8e04aaffb6de5f1ae61de7b671c1531172ccf429 3. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/arch/arm64/boot/dts/qcom/ipq8074.dtsi?h=v5.15.99&id=a55a645aa303a3f7ec37db69822d5420657626da 4. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/arch/arm64/boot/dts/qcom/ipq8074.dtsi?h=v5.15.99&id=d9df682bcea57fa25f37bbf17eae56fa05662635 5. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/arch/arm64/boot/dts/qcom/ipq8074.dtsi?h=v5.15.99&id=7e6eeb5fb3aa9e5feffdb6e137dcc06f5f6410e1 6. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/arch/arm64/boot/dts/qcom/ipq8074.dtsi?h=v5.15.99&id=e88204931d9a60634cd50bbc679f045439c4b91d 7. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/arch/arm64/boot/dts/qcom/ipq8074.dtsi?h=v5.15.99&id=1563af0f28afd3b6d64ac79a2aecced3969c90bf 8. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/arch/arm64/boot/dts/qcom/ipq8074.dtsi?h=v5.15.99&id=feb8c71f015d416f1afe90e1f62cf51e47376c67 9. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/arch/arm64/boot/dts/qcom/ipq8074.dtsi?h=v5.15.99&id=69c7a270357a7d50ffd3471b14c60250041200e3 10. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/arch/arm64/boot/dts/qcom/ipq8074.dtsi?h=v5.15.99&id=dd3d021ae5471d98adf81f1e897431c8657d0a18 Build system: x86_64 Build-tested: bcm2711/RPi4B, ramips/tplink_archer-a6-v3 Run-tested: bcm2711/RPi4B, ramips/tplink_archer-a6-v3 Signed-off-by: John Audia <therealgraysky@proton.me> Tested-by: Robert Marko <robimarko@gmail.com> #ipq807x/Dynalink WRX36 Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> #ipq807x/ax3600, x86_64/FW-7543B, ath79/tl-wdr3600, ipq806x/g10, ipq806x/nbg6817
* layerscape: switch to Kernel 5.15 by defaultPaul Spooren2023-03-171-2/+3
| | | | | | | Getting ready for the next release. Tested-by: Pawel Dembicki <paweldembicki@gmail.com> Signed-off-by: Paul Spooren <mail@aparcar.org>
* kernel: bump 5.15 to 5.15.96John Audia2023-02-281-1/+1
| | | | | | | | | | All patches automatically rebased. Build system: x86_64 Build-tested: bcm2711/RPi4B, filogic/xiaomi_redmi-router-ax6000-ubootmod, ramips/tplink_archer-a6-v3 Run-tested: bcm2711/RPi4B, filogic/xiaomi_redmi-router-ax6000-ubootmod, ramips/tplink_archer-a6-v3 Signed-off-by: John Audia <therealgraysky@proton.me>
* layerscape: Add CONFIG_NVMEM_LAYERSCAPE_SFP kernel configuration optionHauke Mehrtens2023-01-081-0/+1
| | | | | | | | The kernel configuration option is now available on kernel 5.10 and 5.15, add it to the config for 5.15 too. Fixes: 8dfe69cdfc5c ("kernel: update nvmem subsystem to the latest upstream") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: update nvmem subsystem to the latest upstreamRafał Miłecki2023-01-061-0/+1
| | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* tfa-layerscape: Use trusted-firmware-a.mkHauke Mehrtens2022-12-311-14/+14
| | | | | | | | This converts the trusted firmware arm build Makefile to make use of the common trusted-firmware-a.mk file. This also fixes the build with binutils 2.39. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 5.15 to 5.15.83John Audia2022-12-141-1/+1
| | | | | | | | | | | | | | | Removed upstreamed: backport-5.15/883-v6.1-ca8210-Fix-crash-by-zero-initializing-data.patch[1] All patches automatically rebased 1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.15.83&id=246bcd05ba6cc43b34ac0bb4bac3ea94a4efa07c Build system: x86_64 Build-tested: bcm2711/RPi4B Run-tested: bcm2711/RPi4B Signed-off-by: John Audia <therealgraysky@proton.me>
* layerscape: kmod-ppfe: Use ppfe driver as modulePawel Dembicki2022-11-273-5/+5
| | | | | | | | | | | In 8274451cb86 kmod-ppfe was changed to built-in because CONFIG_FSL_PPFE was binary. In 5.10 and 5.15 kernel, PPFE driver can be build as module. This patch switch kmod-ppfe from build-in to loadable module. Loadable module helps to avoid hazard: driver is looking for firmware file before mount root. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* layerscape: switch kernel testing to 5.15Pawel Dembicki2022-11-271-1/+1
| | | | | | | | | Let's test layerscape with 5.15 kernel. Run tested: LS1012A-FRDM, LS1046A-RDB (nor and sd-boot images), LS1021A-IOT (By @ArtelMike with u-boot fix) Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* layerscape: Switch LS1012A-FRDM initramfs to gzipPawel Dembicki2022-11-271-1/+0
| | | | | | | | | | At this moment LS1012A-FRDM have uncompressed initramfs image. Error was caused, because gzip extract area overlap image. Let's change loadaddr and enable gzip initramfs images again. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* layerscape: remove kernel 5.4 dependencesPawel Dembicki2022-11-271-28/+0
| | | | | | 5.4 kernel was removed. Let's clean old dependences. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* layerscape: 5.15: refresh kernel configPawel Dembicki2022-11-272-28/+42
| | | | | | Done by 'make kernel_oldconfig'. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* layerscape: copy patches 5.10 to 5.15Pawel Dembicki2022-11-279-0/+12571
| | | | | | | | | | One patch manually rebased: 302-arm64-dts-ls1012a-update-with-ppfe-support.patch PFE driver patch recreated from NXP 5.15 tree: 701-staging-add-fsl_ppfe-driver.patch Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* layerscape: copy config 5.10 to 5.15Pawel Dembicki2022-11-272-0/+1516
| | | | | | Configs was just copied. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* layerscape: refresh kernel configPawel Dembicki2022-11-272-10/+1
| | | | | | Done by 'make kernel_oldconfig'. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* layerscape: Fix SPI-NOR issues with vendor patchesPawel Dembicki2022-11-274-0/+130
| | | | | | | | | | | | | | | | | | | | For some reason LS1012A and LS1046A devboards don't work well with Spansion SPI NOR flash. It cause read and write errors like: [ 27.285887] jffs2: Newly-erased block contained word 0xc20031985 at offset 0x025ae000 [ 27.468922] jffs2: Newly-erased block contained word 0x0 at offset 0x02573000 [ 27.502615] jffs2: Newly-erased block contained word 0xe723f41e5823f110 at offset 0x02572000 [ 27.541550] jffs2: Newly-erased block contained word 0x1a7d266ee6 at offset 0x02571000 [ 27.577195] jffs2: Newly-erased block contained word 0x5d000bae8d52fec6 at offset 0x02570000 [ 27.611800] jffs2: Newly-erased block contained word 0x63515aee63515a4b at offset 0x0256f000 [ 27.651749] jffs2: Newly-erased block contained word 0xc20031985 at offset 0x0256e000 [ 27.825593] jffs2: Newly-erased block contained word 0xc20031985 at offset 0x0252e000 NXP have found workarround and applied in their vendor kernel version. They force 1x tx and 1x rx lines in qspi. That method fix issues. This patch ports patches from NXP LSDK tree. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* layerscape: armv8_64b: add CONFIG_ARM64_ERRATUM_1742098John Audia2022-10-301-0/+1
| | | | | | | | 5.10.152 introduces a new symbol that applies Cortex-A72 SoCs so enable it[1]. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/arch/arm64/Kconfig?id=v5.10.152&id2=v5.10.151 Signed-off-by: John Audia <therealgraysky@proton.me>
* kernel: disable CONFIG_CPU_LITTLE_ENDIAN in generic configAleksander Jan Bajkowski2022-10-211-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | Endianness depends on CPU architecture. CONFIG_CPU_(BIG/LITTLE)_ENDIAN should be enabled on target or subtarget based on SoC architecture. Fixes warning: $ make kernel_oldconfig CONFIG_TARGET=subtarget ... .config:1008:warning: override: CPU_LITTLE_ENDIAN changes choice state .... Summary: - ARC - only the CONFIG_CPU_BIG_ENDIAN symbol is defined for this architeture. If it is disabled then the processor operates in LITTLE_ENDIAN mode (default), - ARM32 - CONFIG_CPU_LITTLE_ENDIAN symbol available since kernel 5.19. This option should be enabled after OpenWRT moves to kernel 6.x. After refreshing the kernel, the symbol disappears, - ARM64 - enabled CONFIG_CPU_LITTLE_ENDIAN, - MIPS - enabled relevant symbols, - POWERPC - enabled CONFIG_CPU_BIG_ENDIAN, - UML - Symbols are not defined for this architecture, - X86 - always little endian. Symbols are not defined for this architecture. Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
* kernel: remove target specific CONFIG_IKCONFIG linesFelix Fietkau2022-10-142-4/+0
| | | | | | Use generic configuration for this feature Signed-off-by: Felix Fietkau <nbd@nbd.name>
* kernel: Move some IOMMU options to genericHauke Mehrtens2022-09-241-1/+0
| | | | | | | | | | | | This adds some missing IOMMU related options for x86/64 and moves some of them to generic for all targets. On x86 IOMMU_DEFAULT_DMA_LAZY is used by default, on all other platforms IOMMU_DEFAULT_DMA_STRICT is the default. we just follow the default kernel configuration here. Fixes: 8fea4a102ccd ("x86/64: enable IOMMU support") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 5.10 to 5.10.137Petr Štetiar2022-08-231-1/+1
| | | | | | | | | | Removed following upstreamed patch: * bcm53xx: 081-next-ARM_dts_BCM53015-add-mr26.patch All other patches automagically rebased. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* kernel: Activate CONFIG_GPIOLIB in generic configurationHauke Mehrtens2022-08-102-2/+0
| | | | | | | | All targets expect the malta target already activate the CONFIG_GPIOLIB option. Move it to generic kernel configuration and also activate it for malta. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: Activate CONFIG_INPUT_MISC on all targetsHauke Mehrtens2022-08-101-1/+0
| | | | | | | | | CONFIG_INPUT_MISC does not do any changes to the kernel image, it only shows some extra kernel configuration options. Activate it on all targets. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: cut broken SPI_NOR 4K eraseblock LIMIT patchJohn Thomson2022-06-291-1/+0
| | | | | | | | | | | | | | | | | | Since 4e0c54bc5bc8 ("kernel: add support for kernel 5.4"), the spi-nor limit 4k erasesize to spi-nor chips below a configured size patch has not functioned as intended. For uniform erasesize SPI-NOR devices, both nor->erase_opcode & mtd->erasesize are used in erase operations. These are set before, and not modified by, this CONFIG_MTD_SPI_NOR_USE_4K_SECTORS_LIMIT patch. Thus, an SPI-NOR device with CONFIG_MTD_SPI_NOR_USE_4K_SECTORS will always use 4k erasesize (where the device supports it). If this patch was fixed to function as intended, there would be cases where devices change from a 4K to a 64K erasesize. Signed-off-by: John Thomson <git@johnthomson.fastmail.com.au>
* generic: enable CRYPTO_LIB_BLAKE2S[_X86|_ARM]Tomasz Maciej Nowak2022-06-242-0/+3
| | | | | | | | | | | | This is now built-in, enable so it won't propagate on target configs. Link: https://lkml.org/lkml/2022/1/3/168 Fixes: 79e7a2552e89 ("kernel: bump 5.15 to 5.15.44") Fixes: 0ca93670693b ("kernel: bump 5.10 to 5.10.119") Signed-off-by: Tomasz Maciej Nowak <tmn505@gmail.com> (Link to Kernel's commit taht made it built-in, CRYPTO_LIB_BLAKE2S[_ARM|_X86] as it's selectable, 5.10 backport) Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* layerscape/armv8_64b: enable armv8-CE crypto algosEneas U de Queiroz2022-06-041-0/+11
| | | | | | | This enables armv8 crypto extensions version of AES, GHASH, SHA256 and CRC T10 algorithms in the kernel. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
* config: limit CONFIG_DEBUG_INFO to top-level generic configsTony Ambardar2022-05-181-1/+0
| | | | | | | | | | Remove redundant target-level entries, noting that these settings will be configured from "Kernel build options" of Kconfig. Signed-off-by: Tony Ambardar <itugrok@yahoo.com> Signed-off-by: Felix Fietkau <nbd@nbd.name> [remove from new configs introduced after patch submission] Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* layerscape/armv8_64b: enable DEBUG_INFO_REDUCEDStijn Tintel2022-05-181-1/+0
| | | | | | | | | | | | | We currently enable DEBUG_INFO_REDUCED for all targets via the generic kernel config. There is only one subtarget, layerscape/armv8_64b, that overrides this setting. As there is no explanation for this in the commit message that introduced this, and question to its author went unanswered, let's simply drop this symbol from the subtarget config. This way, we have consistency across the tree, and we do not have to introduce a special case when moving this symbol to an OpenWrt kernel config option. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* layerscape: image: drop redundant parameter from kernel build recipePiotr Dymacz2022-04-011-2/+2
| | | | | | | Neither 'fit', nor target-specific 'traverse-fit' build recipes accept FDT load address in 3rd parameter. Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* layerscape: make boot filesystem reproducibleDaniel Golle2022-03-281-1/+3
| | | | | | | Set timestamp option for make_ext4fs to make boot filesystem reproducible. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* kernel: delete Linux 5.4 config and patchesDaniel Golle2022-03-21892-311507/+0
| | | | | | | | As the upcoming release will be based on Linux 5.10 only, remove all kernel configuration as well as patches for Linux 5.4. There were no targets still actively using Linux 5.4. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* kernel: 5.10: remove CONFIG_DEVTMPFS{,_MOUNT} from kconfigsRui Salvaterra2022-03-012-4/+0
| | | | | | They are required for container support, but are handled in Config-kernel.in. Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* kernel: bump 5.4 to 5.4.174John Audia2022-01-287-48/+6
| | | | | | | | | | | | | | Removed upstreamed patches: layerscape/patches-5.4/302-dts-0083-arm64-ls1028a-qds-correct-bus-of-rtc.patch[1] All other patches automatically rebased. 1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.174&id=65816c1034769e714edb70f59a33bc5472d9e55f Build system: x86_64 Build-tested: ramips/mt7621 Signed-off-by: John Audia <graysky@archlinux.us>
* layerscape: switch to 5.10 KernelPaul Spooren2022-01-191-1/+1
| | | | | | | Tested by multiple users and since all targets need to be on Kernel 5.10 to be part of the next release, add changes. Signed-off-by: Paul Spooren <mail@aparcar.org>
* kernel: bump 5.4 to 5.4.172John Audia2022-01-161-1/+1
| | | | | | | | | All patches automatically rebased. Build system: x86_64 Build-tested: ramips/mt7621 Signed-off-by: John Audia <graysky@archlinux.us>
* kernel: bump 5.4 to 5.4.169John Audia2022-01-032-3/+3
| | | | | | | | | | | All patches automatically rebased. Build system: x86_64 Build-tested: ramips/mt7621* *Had to revert 7f1edbd in order to build due to FS#4149 Signed-off-by: John Audia <graysky@archlinux.us>
* kernel: 5.10: consolidate mac80211 crypto optionsSergey Ryazanov2021-12-172-4/+0
| | | | | | | | | | | | | | | | | | | | | | Each of - CRYPTO_AEAD2 - CRYPTO_AEAD - CRYPTO_GF128MUL - CRYPTO_GHASH - CRYPTO_HASH2 - CRYPTO_HASH - CRYPTO_MANAGER2 - CRYPTO_MANAGER - CRYPTO_NULL2 either directly required for mac80211 crypto support, or directly selected by such options. Support for the mac80211 crypto was enabled in the generic config since c7182123b9 ("kernel: make cryptoapi support needed by mac80211 built-in"). So move the above options from the target configs to the generic config to make it clear why do we need them. CC: Felix Fietkau <nbd@nbd.name> Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
* kernel: filter out both Clang and LLD versionsSergey Ryazanov2021-12-172-2/+0
| | | | | | | | Both CLANG_VERSION and LLD_VERISON are autogenerated runtime configuration options, so add them to the kernel configuration filter and remove from generic and per-target configs to keep configs clean. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
* kernel: bump 5.4 to 5.4.167John Audia2021-12-171-1/+1
| | | | | | | | | | | | All patches automatically rebased. Build system: x86_64 Build-tested: ramips/mt7621* *FS#4149 affects me so I had to revert 7f1edbd41295dff9f2127b169fbc086c0fb2c14e in order to downgrade to 2.35.1 Signed-off-by: John Audia <graysky@archlinux.us>
* kernel: bump 5.4 to 5.4.165John Audia2021-12-1727-88/+88
| | | | | | | | | | | | All patches automatically rebased. Build system: x86_64 Build-tested: ramips/mt7621* *FS#4149 affects me so I had to revert 7f1edbd41295dff9f2127b169fbc086c0fb2c14e in order to downgrade to 2.35.1 Signed-off-by: John Audia <graysky@archlinux.us>
* layerscape: armv7: refresh config-5.10Martin Schiller2021-12-131-24/+30
| | | | Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* layerscape: armv7: copy config-5.4 to config-5.10Martin Schiller2021-12-131-0/+673
| | | | Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* layerscape: armv8_64b: refresh config-5.10Martin Schiller2021-12-131-99/+71
| | | | Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* layerscape: armv8_64b: copy config-5.4 to config-5.10Martin Schiller2021-12-131-0/+881
| | | | Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* layerscape: armv8_64b: use non-SDK dts files for linux-5.10 or newerMartin Schiller2021-12-131-0/+24
| | | | | | | Since we decided to drop the LSDK patches with linux-5.10, we now have to switch to the corresponding upstream dts files as well. Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* layerscape: armv8_64b: fix KERNEL_LOADADDR for linux >= 5.8Martin Schiller2021-12-131-0/+4
| | | | | | | | | | In kernel versions newer than 5.8 the arm64 TEXT_OFFSET (0x80000) has been set to 0x0 (and later removed). This will break Uimages with kernel load addresses that aren't 2MiB aligned any longer. Resulting in the kernel silently fail to boot. For layerscape armv8_64b targets this needs to be changed to 0x80000000 (start of RAM). Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* layerscape: add patches for kernel 5.10Martin Schiller2021-12-135-0/+12680
| | | | Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* layerscape: add kernel 5.10 as testing versionMartin Schiller2021-12-131-0/+1
| | | | | | | This patch adds "KERNEL_TESTING_PATCHVER:=5.10" to the Makefile in layerscape target to allow using Kernel 5.10 for testing. Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* layerscape: remove unneeded KERNEL_ENTRY_POINT definitionMartin Schiller2021-12-132-2/+0
| | | | | | As KERNEL_ENTRY_POINT is identical to KERNEL_LOADADDR, drop it. Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* kernel: bump 5.4 to 5.4.162John Audia2021-11-285-14/+15
| | | | | | | | | | | | All patches automatically rebased. Build system: x86_64 Build-tested: ramips/mt7621* *I am hit with the binutils 2.37 bug so I had to revert 7f1edbd41295dff9f2127b169fbc086c0fb2c14e in order to downgrade to 2.35.1 Signed-off-by: John Audia <graysky@archlinux.us>
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-26 18:23:39 +0000