summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2022-03-07 11:43:22 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2022-03-07 11:43:22 -0800
commitea4424be16887a37735d6550cfd0611528dbe5d9 (patch)
tree30f8216215a1cf4dcaf943a1e25d963327a2a86b /Documentation
parent06be3029703fed2099b7247c527ab70d75255178 (diff)
parent42da5a4ba17070e9d99abf375a5bd70e85d2a6b8 (diff)
Merge tag 'mtd/fixes-for-5.17-rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux
Pull MTD fix from Miquel Raynal: "As part of a previous changeset introducing support for the K3 architecture, the OMAP_GPMC (a non visible symbol) got selected by the selection of MTD_NAND_OMAP2 instead of doing so from the architecture directly (like for the other users of these two drivers). Indeed, from a hardware perspective, the OMAP NAND controller needs the GPMC to work. This led to a robot error which got addressed in fix merge into -rc4. Unfortunately, the approach at this time still used "select" and lead to further build error reports (sparc64:allmodconfig). This time we switch to 'depends on' in order to prevent random misconfigurations. The different dependencies will however need a future cleanup" * tag 'mtd/fixes-for-5.17-rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux: mtd: rawnand: omap2: Actually prevent invalid configuration and build error
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions