typesafe callbacks
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest6 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/6 | cast_if_type: allow macros functions which take more than one type.include/ include/ | +21 | 0 replies | |
| 2/6 | typesafe_cb: wrappers for typesafe callbacks.include/ | +35 | 0 replies | |
| 3/6 | typesafe: Convert stop_machineinclude/ kernel/ | +10 | 0 replies | |
| 4/6 | typesafe: kthread_create and kthread_runinclude/ kernel/ | +30 | 0 replies | |
| 5/6 | typesafe: request_irq and devm_request_irqinclude/ kernel/ kernel/ | +20 | 0 replies | |
| 6/6 | typesafe: TIMER_INITIALIZER and setup_timerinclude/ | +22 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/6] typesafe callbacks
The idea is to create a general typesafe callback mechanism which doesn't break compile on existing code and doesn't allow any unsafe callback types.
Al had a very long timer conversion series followed by a different mechanism, and that just covered timers; unfortunately that technique provides insufficient typechecking for the general case (eg. int return types and callback functions which take integer args as well as the data arg).
Note that these typechecks end up being *too* strict in some cases, disallowing some potentially valid cases. But since you can still use the current via-void* method, these corner cases lose nothing.