diff options
author | 2023-02-08 21:32:19 -0800 | |
---|---|---|
committer | 2023-02-08 21:32:20 -0800 | |
commit | 5131a053f2927158fb42880c69b5dc0d2e28ddee (patch) | |
tree | 836543aab7f6259566f3be809c3b31e7177bd6a7 /ipc/syscall.c | |
parent | Merge tag 'mlx5-next-netdev-deadlock' of git://git.kernel.org/pub/scm/linux/k... (diff) | |
parent | can: bittiming: can_calc_bittiming(): add missing parameter to no-op function (diff) | |
download | linux-5131a053f2927158fb42880c69b5dc0d2e28ddee.tar.gz linux-5131a053f2927158fb42880c69b5dc0d2e28ddee.tar.bz2 linux-5131a053f2927158fb42880c69b5dc0d2e28ddee.zip |
Merge tag 'linux-can-next-for-6.3-20230208' of git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can-next
Marc Kleine-Budde says:
====================
can-next 2023-02-08
The 1st patch is by Oliver Hartkopp and cleans up the CAN_RAW's
raw_setsockopt() for CAN_RAW_FD_FRAMES.
The 2nd patch is by me and fixes the compilation if
CONFIG_CAN_CALC_BITTIMING is disabled. (Problem introduced in last
pull request to next-next.)
* tag 'linux-can-next-for-6.3-20230208' of git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can-next:
can: bittiming: can_calc_bittiming(): add missing parameter to no-op function
can: raw: use temp variable instead of rolling back config
====================
Link: https://lore.kernel.org/r/20230208210014.3169347-1-mkl@pengutronix.de
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'ipc/syscall.c')
0 files changed, 0 insertions, 0 deletions