diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2019-02-08 10:53:44 -0800 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2019-02-08 10:53:44 -0800 |
commit | 8c8e62cc983938a554d39497b5600b842f8a7965 (patch) | |
tree | fe882134f2634f9bc24de89e2b9acb8980fdb20c /kernel/backtracetest.c | |
parent | e464f50c057a1fbefae6c6078f9bd5511f84f199 (diff) | |
parent | 36991ca68db9dd43bac7f3519f080ee3939263ef (diff) | |
download | blackbird-obmc-linux-8c8e62cc983938a554d39497b5600b842f8a7965.tar.gz blackbird-obmc-linux-8c8e62cc983938a554d39497b5600b842f8a7965.zip |
Merge tag 'driver-core-5.0-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core
Pull driver core fixes from Greg KH:
"Here are some driver core fixes for 5.0-rc6.
Well, not so much "driver core" as "debugfs". There's a lot of
outstanding debugfs cleanup patches coming in through different
subsystem trees, and in that process the debugfs core was found that
it really should return errors when something bad happens, to prevent
random files from showing up in the root of debugfs afterward. So
debugfs was fixed up to handle this properly, and then two fixes for
the relay and blk-mq code was needed as it was making invalid
assumptions about debugfs return values.
There's also a cacheinfo fix in here that resolves a tiny issue.
All of these have been in linux-next for over a week with no reported
problems"
* tag 'driver-core-5.0-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core:
blk-mq: protect debugfs_create_files() from failures
relay: check return of create_buf_file() properly
debugfs: debugfs_lookup() should return NULL if not found
debugfs: return error values, not NULL
debugfs: fix debugfs_rename parameter checking
cacheinfo: Keep the old value if of_property_read_u32 fails
Diffstat (limited to 'kernel/backtracetest.c')
0 files changed, 0 insertions, 0 deletions