emo/busybox
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

i2cdump: don't use common_bufsiz1

Browse Source 
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>
This commit is contained in:
Bartosz Golaszewski 2016-06-23 17:19:50 +02:00 committed by Denys Vlasenko
parent 4d5acd2d42
commit 59f8197624
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
miscutils/i2c_tools.c
View File

@ -908,7 +908,7 @@ int i2cdump_main(int argc UNUSED_PARAM, char **argv)
int bus_num, bus_addr, mode = I2C_SMBUS_BYTE_DATA, even = 0, pec = 0;
unsigned first = 0x00, last = 0xff, opts;
int *block = (int *)bb_common_bufsiz1;
int block[I2CDUMP_NUM_REGS];
char *opt_r_str, *dash;
int fd, res;