i2cdump: don't use common_bufsiz1
authorBartosz Golaszewski <bartekgola@gmail.com>
Thu, 23 Jun 2016 15:19:50 +0000 (17:19 +0200)
committerDenys Vlasenko <vda.linux@googlemail.com>
Fri, 24 Jun 2016 01:58:43 +0000 (03:58 +0200)
commit59f81976249a85cf02bd73c2395f018033069466
tree85cefceec2a7edea58ebba3d6f2ea86d489e8685
parent4d5acd2d4264d0a754d3d11c94825fd69d0c7837
i2cdump: don't use common_bufsiz1

Commit e6a2f4cc changed the way common_bufsiz1 works. Now it needs to
be initialized before using, but i2cdump wasn't updated by said patch.

Since the fact that we're using common_bufsiz1 here isn't obvious (no
G_INIT() macro, no other global variables), drop it and simply
allocate the integer array required for block reads on the stack.

Tested with i2c block read on a Lenovo Thinkpad laptop.

Signed-off-by: Bartosz Golaszewski <bartekgola@gmail.com>
Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
miscutils/i2c_tools.c