On Sat, Mar 17, 2018 at 02:48:40PM -0400, J. Bruce Fields wrote: > This is a pretty simple patch that touches a lot of files. What's the > procedure for handling patches like this? I haven't had to do this > before. I'm not sure it's a good idea. We want it opaque - if anything, I would prefer to have anything mistakenly passing it to a function that takes a pointer scream like hell at build time. The current variant doesn't have such protection, but it can at least be grepped for. void * can't. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
