RFC: Typesafe callbacks
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest6 patches 16 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/6 | typesafe: Convert stop_machine and callersdrivers/ include/ kernel/ +1 more | +15 | 0 replies | |
| 2/6 | typesafe: kthread_create and kthread_runinclude/ kernel/ | +32 | 6 replies | |
| 3/6 | typesafe: convert kthread userscrypto/ crypto/ drivers/ +67 more | +104 | 0 replies | |
| 4/6 | typesafe: cast_if_type to allow macros functions which take more than one type.include/ include/ | +19 | 0 replies | |
| 5/6 | typesafe: request_irq and devm_request_irqinclude/ kernel/ kernel/ | +23 | 0 replies | |
| 6/6 | typesafe: timersinclude/ | +16 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/6] RFC: Typesafe callbacks
Hi all,
Converting to and from void * for callback functions loses type safety:
everywhere else we expect the compiler to catch incorrect pointer types handed to functions.
It's pretty simple to create typesafe callback functions using typeof, and
with a little gcc trickery we can allow both old-style and typesafe callbacks to avoid churn on commonly-used routines.
Feedback welcomed,
Rusty.