The best way is by context and example. Figure out what the driver code is trying to accomplish and see how that fits in with the new macro. If you can't do that you can check the kernel's changelists ...
Some results have been hidden because they may be inaccessible to you
Show inaccessible results
Feedback