Hello btrfs-progs, can we move the min/max macros away from libbtrfs public API? This may cause conflict while compiling i.e. snapper with gcc 6.0 (aka with -std=gnu++14). The thing is I don't see a point why those macros should be kept in kerncompat.h at all. Such macros are used solely in btrfs-progs internals and there's no need to expose them in API.
Kind regards Ondrej Ondrej Kozina (1): btrfs-progs: libbtrfs: remove max/min macros from API backref.c | 1 + ctree.c | 1 + extent_io.c | 1 + file-item.c | 1 + free-space-cache.c | 1 + inode-map.c | 1 + internal.h | 42 ++++++++++++++++++++++++++++++++++++++++++ kerncompat.h | 20 -------------------- utils.h | 1 + 9 files changed, 49 insertions(+), 20 deletions(-) create mode 100644 internal.h -- 2.4.3 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
