aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/au1000
diff options
context:
space:
mode:
authorRafał Miłecki <rafal@milecki.pl>2018-04-05 11:08:27 +0200
committerRafał Miłecki <rafal@milecki.pl>2018-04-05 11:12:49 +0200
commitafca23558a2fbfb2cb044ec69bfb9a7447121927 (patch)
treec3adc5ac97092fe4b1607674b29ec3f346fcaf1a /target/linux/au1000
parentba502a49a7e4b140ef177cc69db91e8e2eb4069e (diff)
downloadupstream-afca23558a2fbfb2cb044ec69bfb9a7447121927.tar.gz
upstream-afca23558a2fbfb2cb044ec69bfb9a7447121927.tar.bz2
upstream-afca23558a2fbfb2cb044ec69bfb9a7447121927.zip
kernel: backport commit reverting genirq patch causing regressions
Switching from kernel 4.4.120 to 4.4.124 introduced a regression in the genirq code. It was caused by a commit 9d0273bb1c4b6 ("genirq: Use irqd_get_trigger_type to compare the trigger type for shared IRQs"). On bcm53xx it breaks serial console and results in a flood of: [ 22.078829] genirq: Flags mismatch irq 18. 00000080 (serial) vs. 00000080 (gpio) [ 22.086432] genirq: Flags mismatch irq 18. 00000080 (serial) vs. 00000080 (gpio) [ 22.601150] genirq: Flags mismatch irq 18. 00000080 (serial) vs. 00000080 (gpio) [ 22.608845] genirq: Flags mismatch irq 18. 00000080 (serial) vs. 00000080 (gpio) Later in the upstream "linux-4.4.y" branch that commit was reverted and it was followed by a 4.4.126 release. Until we switch from 4.4.124 to 4.4.126 (or newer), let's backport that reverting commit. Fixes: bed0ee7cbfaa5 ("Kernel: bump 4.4 to 4.4.124 for 17.01") Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Diffstat (limited to 'target/linux/au1000')
0 files changed, 0 insertions, 0 deletions