From: Wolfram Sang <wsa@the-dreams.de>
To: Bing Sun <sunbing@redflag-linux.com>
Cc: gregkh@linuxfoundation.org, wsa+renesas@sang-engineering.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
sunbing.linux@gmail.com
Subject: Re: [PATCH] Staging: ks7010: michael_mic: fixed macros coding style issue
Date: Wed, 20 Jul 2016 18:02:21 +0200 [thread overview]
Message-ID: <20160720160221.GJ1688@katana> (raw)
In-Reply-To: <1468893066-4712-1-git-send-email-sunbing@redflag-linux.com>
[-- Attachment #1: Type: text/plain, Size: 1791 bytes --]
On Tue, Jul 19, 2016 at 09:51:06AM +0800, Bing Sun wrote:
> Fixed coding style issue:
> Enclose multiple statements macros definition in a do while loop.
> Use one space around binary operators.
>
> Signed-off-by: Bing Sun <sunbing@redflag-linux.com>
Looks good for what it is. One comment below. I will test this tomorrow.
> ---
> drivers/staging/ks7010/michael_mic.c | 20 +++++++++++++-------
> 1 file changed, 13 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/staging/ks7010/michael_mic.c b/drivers/staging/ks7010/michael_mic.c
> index e14c109..d332678 100644
> --- a/drivers/staging/ks7010/michael_mic.c
> +++ b/drivers/staging/ks7010/michael_mic.c
> @@ -20,15 +20,21 @@
> #define getUInt32( A, B ) (uint32_t)(A[B+0] << 0) + (A[B+1] << 8) + (A[B+2] << 16) + (A[B+3] << 24)
>
> // Convert from UInt32 to Byte[] in a portable way
> -#define putUInt32( A, B, C ) A[B+0] = (uint8_t) (C & 0xff); \
> - A[B+1] = (uint8_t) ((C>>8) & 0xff); \
> - A[B+2] = (uint8_t) ((C>>16) & 0xff); \
> - A[B+3] = (uint8_t) ((C>>24) & 0xff)
> +#define putUInt32(A, B, C) \
> +do { \
> + A[B + 0] = (uint8_t)(C & 0xff); \
> + A[B + 1] = (uint8_t)((C >> 8) & 0xff); \
> + A[B + 2] = (uint8_t)((C >> 16) & 0xff); \
> + A[B + 3] = (uint8_t)((C >> 24) & 0xff); \
> +} while (0)
We surely have helper functions for this in the kernel?
>
> // Reset the state to the empty message.
> -#define MichaelClear( A ) A->L = A->K0; \
> - A->R = A->K1; \
> - A->nBytesInM = 0;
> +#define MichaelClear(A) \
> +do { \
> + A->L = A->K0; \
> + A->R = A->K1; \
> + A->nBytesInM = 0; \
> +} while (0)
>
> static
> void MichaelInitializeFunction(struct michel_mic_t *Mic, uint8_t * key)
> --
> 2.1.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-07-20 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 1:51 [PATCH] Staging: ks7010: michael_mic: fixed macros coding style issue Bing Sun
2016-07-20 16:02 ` Wolfram Sang [this message]
2016-07-21 16:57 ` Wolfram Sang
-- strict thread matches above, loose matches on Subject: below --
2016-07-18 4:35 Sunbing
2016-07-18 12:10 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160720160221.GJ1688@katana \
--to=wsa@the-dreams.de \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sunbing.linux@gmail.com \
--cc=sunbing@redflag-linux.com \
--cc=wsa+renesas@sang-engineering.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox