diff options
| author | Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com> | 2021-02-27 16:00:24 -0800 |
|---|---|---|
| committer | Adrian Schmutzler <freifunk@adrianschmutzler.de> | 2021-03-06 11:24:12 +0100 |
| commit | ef1e6520164e19451bc9cb8275cf293a699e1684 (patch) | |
| tree | bd6e06143301ff02a4432227671fb0ec3e781d3d /target/linux/ramips/patches-5.10/315-owrt-hack-fix-mt7688-cache-issue.patch | |
| parent | 3149d8e7be6539897e9f3873ed9a2b9213a798a9 (diff) | |
| download | upstream-ef1e6520164e19451bc9cb8275cf293a699e1684.tar.gz upstream-ef1e6520164e19451bc9cb8275cf293a699e1684.tar.bz2 upstream-ef1e6520164e19451bc9cb8275cf293a699e1684.zip | |
ramips: 5.10: rename patches to follow guide
Rename patches to follow the 3-digit classification from the OpenWrt
Developer Guide.
https://openwrt.org/docs/guide-developer/build-system/use-patches-with-buildsystem#naming_patches
Signed-off-by: Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com>
Diffstat (limited to 'target/linux/ramips/patches-5.10/315-owrt-hack-fix-mt7688-cache-issue.patch')
| -rw-r--r-- | target/linux/ramips/patches-5.10/315-owrt-hack-fix-mt7688-cache-issue.patch | 29 |
1 files changed, 29 insertions, 0 deletions
diff --git a/target/linux/ramips/patches-5.10/315-owrt-hack-fix-mt7688-cache-issue.patch b/target/linux/ramips/patches-5.10/315-owrt-hack-fix-mt7688-cache-issue.patch new file mode 100644 index 0000000000..bedea14506 --- /dev/null +++ b/target/linux/ramips/patches-5.10/315-owrt-hack-fix-mt7688-cache-issue.patch @@ -0,0 +1,29 @@ +From 5ede027f6c4a57ed25da872420508b7f1168b36b Mon Sep 17 00:00:00 2001 +From: John Crispin <blogic@openwrt.org> +Date: Mon, 7 Dec 2015 17:15:32 +0100 +Subject: [PATCH 13/53] owrt: hack: fix mt7688 cache issue + +Signed-off-by: John Crispin <blogic@openwrt.org> +--- + arch/mips/kernel/setup.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +--- a/arch/mips/kernel/setup.c ++++ b/arch/mips/kernel/setup.c +@@ -723,8 +723,6 @@ static void __init arch_mem_init(char ** + memblock_reserve(crashk_res.start, + crashk_res.end - crashk_res.start + 1); + #endif +- device_tree_init(); +- + /* + * In order to reduce the possibility of kernel panic when failed to + * get IO TLB memory under CONFIG_SWIOTLB, it is better to allocate +@@ -841,6 +839,7 @@ void __init setup_arch(char **cmdline_p) + + cpu_cache_init(); + paging_init(); ++ device_tree_init(); + } + + unsigned long kernelsp[NR_CPUS]; |