[PATCH v5 0/6] fs/seq_file: introduce seq_hex_dump() helper

[Andy Shevchenko]

This introduces a new helper and switches current users to use it. All patches
are compiled tested, kmemleak is tested by its own test suit.

Changelog v5:
- remove already applied patches (hexdump)
- postpone patch for saa7164 since conficts (needs investigation)
- rebase on top of recent linux-next

Changelog v4:
- hexdump is amended to return value from which we can check an overflow
 (patches 1/12 - 4/12)
- seq_hex_dump pushes bytes directly to buffer and returns an error in case of
  overflow (addresses Al Viro's comment)
- append Acked-by for patches 8/12 and 9/12
- convert more users (patches 10/12 - 12/12)

Changelog v3:
- append Mauro's Ack
- rebase on top of recent linux-next

Changelog v2:
- append Acked-by and Reviewed-by tags
- update commit messages in patches 3/5. and 5/5
- update line size to be 32 bytes instead of 16 in patch 3/5
- Joe found that output is changed in patch 4/5, thus I update commit message
  there

Andy Shevchenko (6):
  seq_file: provide an analogue of print_hex_dump()
  crypto: qat - use seq_hex_dump() to dump buffers
  parisc: use seq_hex_dump() to dump buffers
  [S390] zcrypt: use seq_hex_dump() to dump buffers
  kmemleak: use seq_hex_dump() to dump buffers
  wil6210: use seq_hex_dump() to dump buffers

 .../crypto/qat/qat_common/adf_transport_debug.c    | 16 ++-------
 drivers/net/wireless/ath/wil6210/debugfs.c         | 35 ++++--------------
 drivers/parisc/ccio-dma.c                          | 13 ++-----
 drivers/parisc/sba_iommu.c                         |  9 ++---
 drivers/s390/crypto/zcrypt_api.c                   | 10 +-----
 fs/seq_file.c                                      | 42 ++++++++++++++++++++++
 include/linux/seq_file.h                           |  4 +++
 mm/kmemleak.c                                      | 21 ++++-------
 8 files changed, 67 insertions(+), 83 deletions(-)

-- 
2.1.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/