[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <55313413.2050604@c-s.fr>
Date: Fri, 17 Apr 2015 18:25:55 +0200
From: leroy christophe <christophe.leroy@....fr>
To: David Laight <David.Laight@...LAB.COM>,
Kim Phillips <kim.phillips@...escale.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
David S Miller <davem@...emloft.net>
CC: "linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>
Subject: Re: [PATCH v3 03/17] crypto: talitos - talitos_ptr renamed ptr for
more lisibility
Le 17/04/2015 17:14, David Laight a écrit :
> From: Christophe Leroy
>> Linux CodyingStyle recommends to use short variables for local
>> variables. ptr is just good enough for those 3 lines functions.
>> It helps keep single lines shorter than 80 characters.
> ...
>> -static void to_talitos_ptr(struct talitos_ptr *talitos_ptr, dma_addr_t dma_addr)
>> +static void to_talitos_ptr(struct talitos_ptr *ptr, dma_addr_t dma_addr)
>> {
>> - talitos_ptr->ptr = cpu_to_be32(lower_32_bits(dma_addr));
>> - talitos_ptr->eptr = upper_32_bits(dma_addr);
>> + ptr->ptr = cpu_to_be32(lower_32_bits(dma_addr));
>> + ptr->eptr = upper_32_bits(dma_addr);
>> }
> ...
>
> Maybe, but 'ptr' isn't a good choice.
>
>
Any suggestion ?
Christophe
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists