diff options
| author | Jarkko Nikula <[email protected]> | 2022-05-12 15:41:44 +0300 |
|---|---|---|
| committer | Marc Kleine-Budde <[email protected]> | 2022-05-14 20:53:01 +0200 |
| commit | d6da7881020f9b37edb80ada12ce9b50b9232dc1 (patch) | |
| tree | b8d4c42c1d8983078b61761962c7a167d43b055e /lib/test_fortify/write_overflow-strlcpy-src.c | |
| parent | 14ea4a470494528c7e88da5c4116c24eb027059f (diff) | |
can: m_can: remove support for custom bit timing, take #2
Now when Intel Elkhart Lake uses again common bit timing and there are
no other users for custom bit timing, we can bring back the changes
done by the commit 0ddd83fbebbc ("can: m_can: remove support for
custom bit timing").
This effectively reverts commit ea768b2ffec6 ("Revert "can: m_can:
remove support for custom bit timing"") while taking into account
commit ea22ba40debe ("can: m_can: make custom bittiming fields const")
and commit 7d4a101c0bd3 ("can: dev: add sanity check in
can_set_static_ctrlmode()").
Link: https://lore.kernel.org/all/[email protected]
Signed-off-by: Jarkko Nikula <[email protected]>
Signed-off-by: Marc Kleine-Budde <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strlcpy-src.c')
0 files changed, 0 insertions, 0 deletions