On Mon, 2019-06-17 at 12:04 +1000, Alastair D'Silva wrote:
From: Alastair D'Silva <redacted>
Apologies for the large CC list, it's a heads up for those responsible
for subsystems where a prototype change in generic code causes a change
in those subsystems.
This series enhances hexdump.
Still not a fan of these patches.
These improve the readability of the dumped data in certain situations
(eg. wide terminals are available, many lines of empty bytes exist, etc).
Changing hexdump's last argument from bool to int is odd.
Perhaps a new function should be added instead of changing
the existing hexdump.
The default behaviour of hexdump is unchanged, however, the prototype
for hex_dump_to_buffer() has changed, and print_hex_dump() has been
renamed to print_hex_dump_ext(), with a wrapper replacing it for
compatibility with existing code, which would have been too invasive to
change.
Hexdump selftests have be run & confirmed passed.