diff options
| author | Christian Lamparter <chunkeey@gmail.com> | 2022-06-06 21:41:07 +0200 |
|---|---|---|
| committer | Christian Lamparter <chunkeey@gmail.com> | 2022-06-19 12:31:02 +0200 |
| commit | ac2166b1358b1cfe5b6397f027556f7327063c3e (patch) | |
| tree | fe04b3d8c74762c6df393c45d31d004d38c2cb76 /target/linux/mpc85xx/p1010 | |
| parent | 9379bc2fcf905568ef329a121c8c8a11fc98b02c (diff) | |
| download | upstream-ac2166b1358b1cfe5b6397f027556f7327063c3e.tar.gz upstream-ac2166b1358b1cfe5b6397f027556f7327063c3e.tar.bz2 upstream-ac2166b1358b1cfe5b6397f027556f7327063c3e.zip | |
kernel: move Toshiba-TC58NVG0S3H patch to ipq40xx redux
Linux' upstream MTD-Maintainer Miquèl Raynal noted:
|Reverting seems the safest option here, not knowing how many devices
|have these damaged/counterfeit chips. If it is just a couple and only on
|Fritzboxes, as suggested in the Github issue this patch could be
|carried through OpenWrt and that would seem more future proof IMHO.
This patch follows up with the first patch. It actually
moves the patches out of target/linux/generic/pending into
the ipq40xx's patch heap and adds a little note what happend.
For more information, discussions or reports about bad TC58NVG0S3Hs,
please visit the OpenWrt's Github Issue #9962:
<https://github.com/openwrt/openwrt/issues/9962>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
Diffstat (limited to 'target/linux/mpc85xx/p1010')
0 files changed, 0 insertions, 0 deletions