diff options
| author | Vincent Mailhol <mailhol.vincent@wanadoo.fr> | 2021-09-18 11:56:34 +0200 |
|---|---|---|
| committer | Marc Kleine-Budde <mkl@pengutronix.de> | 2021-10-24 16:24:29 +0200 |
| commit | da45a1e4d7b9d6b5a8231acb812df719fe3228b4 (patch) | |
| tree | a5c40e1ea130638957d6510fd4d2164de62e74b5 /include/uapi/Kbuild | |
| parent | can: bittiming: change unit of TDC parameters to clock periods (diff) | |
| download | linux-da45a1e4d7b9d6b5a8231acb812df719fe3228b4.tar.xz linux-da45a1e4d7b9d6b5a8231acb812df719fe3228b4.zip | |
can: bittiming: change can_calc_tdco()'s prototype to not directly modify priv
The function can_calc_tdco() directly retrieves can_priv from the
net_device and directly modifies it.
This is annoying for the upcoming patch. In
drivers/net/can/dev/netlink.c:can_changelink(), the data bittiming are
written to a temporary structure and memcpyed to can_priv only after
everything succeeded. In the next patch, where we will introduce the
netlink interface for TDC parameters, we will add a new TDC block
which can potentially fail. For this reason, the data bittiming
temporary structure has to be copied after that to-be-introduced TDC
block. However, TDC also needs to access data bittiming information.
We change the prototype so that the data bittiming structure is passed
to can_calc_tdco() as an argument instead of retrieving it from
priv. This way can_calc_tdco() can access the data bittiming before it
gets memcpyed to priv.
Link: https://lore.kernel.org/all/20210918095637.20108-4-mailhol.vincent@wanadoo.fr
Signed-off-by: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions