Re: [Cluster-devel] [PATCH 10/11] gfs2: Clean up assertion, consistency check, and error reporting functions

2019-01-14 Thread Bob Peterson
- Original Message - > Instead of passing the __func__, __FILE__, and __LINE__ pre-processor macros > to > each of those functions, print the location of the caller via: > > printk(%pS", (void *)_RET_IP_). > > This gives enough context information to locate where in the code an error >

[Cluster-devel] [PATCH 10/11] gfs2: Clean up assertion, consistency check, and error reporting functions

2019-01-11 Thread Andreas Gruenbacher
Instead of passing the __func__, __FILE__, and __LINE__ pre-processor macros to each of those functions, print the location of the caller via: printk(%pS", (void *)_RET_IP_). This gives enough context information to locate where in the code an error occurred, and reduces the code size by about