summaryrefslogtreecommitdiff
path: root/Documentation/networking/ipv6.txt
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2018-04-27 10:12:20 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2018-04-27 10:12:20 -0700
commitee3748be5c18db11f17baebf50405bbebeb85471 (patch)
tree1672b06dee757f6d8a286c4bc92af9aa7bd70432 /Documentation/networking/ipv6.txt
parentb52c85a7b78938cbb44eb3c536f5f70426a238ae (diff)
parentb93815d0f37e7c4a056a143e6d782abc084ea56b (diff)
Merge tag 'driver-core-4.17-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core
Pull driver core fixes from Greg Kroah-Hartman: "Here are some small driver core and firmware fixes for 4.17-rc3 There's a kobject WARN() removal to make syzkaller a lot happier about some "normal" error paths that it keeps hitting, which should reduce the number of false-positives we have been getting recently. There's also some fimware test and documentation fixes, and the coredump() function signature change that needed to happen after -rc1 before drivers started to take advantage of it. All of these have been in linux-next with no reported issues" * tag 'driver-core-4.17-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core: firmware: some documentation fixes selftests:firmware: fixes a call to a wrong function name kobject: don't use WARN for registration failures firmware: Fix firmware documentation for recent file renames test_firmware: fix setting old custom fw path back on exit, second try test_firmware: Install all scripts drivers: change struct device_driver::coredump() return type to void
Diffstat (limited to 'Documentation/networking/ipv6.txt')
0 files changed, 0 insertions, 0 deletions