Fixed incosistent spacing around arithmetic operator.
Signed-off-by: Jonathan Bowie eudjtb@gmail.com --- drivers/staging/greybus/tools/loopback_test.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/greybus/tools/loopback_test.c b/drivers/staging/greybus/tools/loopback_test.c index 18d7a3d..d5bb8d2 100644 --- a/drivers/staging/greybus/tools/loopback_test.c +++ b/drivers/staging/greybus/tools/loopback_test.c @@ -476,7 +476,7 @@ int format_output(struct loopback_test *t, r->gbphy_firmware_latency_jitter);
} else { - len += snprintf(&buf[len], buf_len- len, ",%s,%s,%u,%u,%u", + len += snprintf(&buf[len], buf_len - len, ",%s,%s,%u,%u,%u", t->test_name, dev_name, t->size, t->iteration_max, r->error);
On Wed, Mar 01, 2017 at 02:09:43AM -0800, Jonathan Bowie wrote:
Fixed incosistent spacing around arithmetic operator.
Signed-off-by: Jonathan Bowie eudjtb@gmail.com
This looks good except that you now dropped the changelog again (what changed in v2 and v3?), and you CC:d the linux-next rather than the staging list devel@driverdev.osuosl.org (I included the address in my response to v1).
You can use scripts/get_maintainer.pl on a patch to figure out which parties and lists to CC (you don't need to include LKML in this case).
Since you're doing this to learn the process, you can send a v4 and get everything right.
Thanks, Johan