diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2020-04-26 11:04:15 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2020-04-26 11:04:15 -0700 |
commit | a8a0e2a96b7dcf7065f97db915e2deb92bf56634 (patch) | |
tree | 3387155e19a1f7476d3f70892927386e68714f44 /MAINTAINERS | |
parent | 749f04615a3d435e98a13cc1e38be10774e1c64b (diff) | |
parent | 5a3577039cbe0bbb8e7a12d2790e23039b8a8618 (diff) | |
download | linux-stable-a8a0e2a96b7dcf7065f97db915e2deb92bf56634.tar.gz linux-stable-a8a0e2a96b7dcf7065f97db915e2deb92bf56634.tar.bz2 linux-stable-a8a0e2a96b7dcf7065f97db915e2deb92bf56634.zip |
Merge tag 'driver-core-5.7-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core
Pull driver core fixes from Greg KH:
"Here are some small firmware/driver core/debugfs fixes for 5.7-rc3.
The debugfs change is now possible as now the last users of
debugfs_create_u32() have been fixed up in the different trees that
got merged into 5.7-rc1, and I don't want it creeping back in.
The firmware changes did cause a regression in linux-next, so the
final patch here reverts part of that, re-exporting the symbol to
resolve that issue. All of these patches, with the exception of the
final one, have been in linux-next with only that one reported issue"
* tag 'driver-core-5.7-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core:
firmware_loader: revert removal of the fw_fallback_config export
debugfs: remove return value of debugfs_create_u32()
firmware_loader: remove unused exports
firmware: imx: fix compile-testing
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions