summaryrefslogtreecommitdiff
path: root/tools/testing/selftests/memfd
diff options
context:
space:
mode:
authorArend van Spriel <aspriel@gmail.com>2018-04-09 00:57:07 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2018-04-19 10:48:32 +0300
commited4564babeeee4fb19fe4ec0beabe29754e380f9 (patch)
treea75c9fe5f002d598a13e759ead3972ec91ebe0eb /tools/testing/selftests/memfd
parent60cc43fc888428bb2f18f08997432d426a243338 (diff)
downloadlinux-ed4564babeeee4fb19fe4ec0beabe29754e380f9.tar.xz
drivers: change struct device_driver::coredump() return type to void
Upon submitting a patch for mwifiex [1] it was discussed whether this callback function could fail. To keep things simple there is no need for the error code so the driver can do the task synchronous or not without worries. Currently the device driver core already ignores the return value so changing it to void. [1] https://patchwork.kernel.org/patch/10231933/ Signed-off-by: Arend van Spriel <aspriel@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/testing/selftests/memfd')
0 files changed, 0 insertions, 0 deletions