When preparing kprobe patches for review and submission, at what sort of granularity is it useful to break them down into? E.g. this patch currently has 6 simulation functions, 6 emulation functions and about 12 decode tables. I could do:
a. one big patch
b. 3 patches, one each for simulation functions, emulation functions, and decode tables
c. 24 patches, one for each function / table.
d. more like I wrote it, a patch for each table and include the functions as they first get used in the tables.
e. even more like I wrote it, a patch for each instruction form as it is added (40+ patches?)
It's not clear to me which of these makes it easier to review, or worth the effort, Any advice?