summaryrefslogtreecommitdiff
path: root/drivers/parisc/pdc_stable.c
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2023-02-09 08:32:19 +0300
committerJakub Kicinski <kuba@kernel.org>2023-02-09 08:32:20 +0300
commit5131a053f2927158fb42880c69b5dc0d2e28ddee (patch)
tree836543aab7f6259566f3be809c3b31e7177bd6a7 /drivers/parisc/pdc_stable.c
parent9245b518c89fcc38f189a734cd0b78ba61a68d89 (diff)
parent65db3d8b5231bd430c12150258125aca155aea97 (diff)
downloadlinux-5131a053f2927158fb42880c69b5dc0d2e28ddee.tar.xz
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 'drivers/parisc/pdc_stable.c')
0 files changed, 0 insertions, 0 deletions