typesafe callbacks
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | typesafe: cast_if_type: allow macros functions which take more than one type.include/ include/ | +20 | 0 replies | |
| 2/4 | typesafe: typesafe_cb: wrappers for typesafe callbacks.include/ | +35 | 0 replies | |
| 3/4 | typesafe: kthread_create and kthread_runinclude/ kernel/ | +30 | 0 replies | |
| 4/4 | typesafe: TIMER_INITIALIZER and setup_timerinclude/ | +23 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/4] typesafe callbacks
It's possible to portably make callbacks typesafe, as well as taking the existing void * arg. This makes the callers more readable and more typesafe.
Done in a way that doesn't break non-gcc: they just don't get a warning.
Been in linux-next for about two full cycles now, and I really want to start using this in my own code.
Thanks,
Rusty.