Manish Katiyar wrote: > Below patch removes errors generated by checkpatch.pl in > kernel/acct.c. Caught by Ingo's code-quality script. Bad changelog: Just say that this is a whitespace adjustment. > @@ -416,7 +416,7 @@ static comp_t encode_comp_t(unsigned long value) > #define MANTSIZE2 20 /* 20 bit mantissa. */ > #define EXPSIZE2 5 /* 5 bit base 2 exponent. */ > #define MAXFRACT2 ((1ul << MANTSIZE2) - 1) /* Maximum > fractional value. */ Your MUA inserted line wraps where there should none. This won't apply as a patch anymore. > @@ -513,13 +514,13 @@ static void do_acct_process(struct bsd_acct_struct *acct, > + current->group_leader->start_time.tv_nsec; > /* convert nsec -> AHZ */ > elapsed = nsec_to_AHZ(run_time); > -#if ACCT_VERSION==3 > +#if ACCT_VERSION == 3 > ac.ac_etime = encode_float(elapsed); > #else > ac.ac_etime = encode_comp_t(elapsed < (unsigned long) -1l ? > - (unsigned long) elapsed : (unsigned long) -1l); > + (unsigned long) elapsed:(unsigned long) -1l); Should IMO be (unsigned long)elapsed : (unsigned long)-1l); or simply stay as it was. But more importantly, the whole expression looks bogus to me. elapsed is an u64 and thus clearly defined regarding its size, while unsigned long will have different sizes on different CPU architectures. Is this intentional? -- Stefan Richter -=====-==--= --=- =---- http://arcgraph.de/sr/ -- To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
