From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Abhirup Deb <abhirupdeb@linux.vnet.ibm.com>,
Martyn Welch <martyn@welchs.me.uk>,
Manohar Vanga <manohar.vanga@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH] staging: vme_user: Add spaces around "<<"
Date: Wed, 14 Dec 2022 08:00:35 +0100 [thread overview]
Message-ID: <c1887a83-25c2-0979-e790-04cdd5ad4aec@gmail.com> (raw)
In-Reply-To: <Y5jYuKfm9d59h6bd@li-27defe4c-32e1-11b2-a85c-e202e9981075.ibm.com>
On 12/13/22 20:55, Abhirup Deb wrote:
> Add spaces around the "<<" in adherence to the Linux kernel coding-style.
> The issues were reported by checkpatch.pl.
>
> Signed-off-by: Abhirup Deb <abhirupdeb@linux.vnet.ibm.com>
> ---
> drivers/staging/vme_user/vme.h | 28 ++++++++++++++--------------
> 1 file changed, 14 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/staging/vme_user/vme.h b/drivers/staging/vme_user/vme.h
> index 98da8d039d60..a74724457d29 100644
> --- a/drivers/staging/vme_user/vme.h
> +++ b/drivers/staging/vme_user/vme.h
> @@ -54,20 +54,20 @@ enum vme_resource_type {
> #define VME_R_ROBIN_MODE 0x1
> #define VME_PRIORITY_MODE 0x2
>
> -#define VME_DMA_PATTERN (1<<0)
> -#define VME_DMA_PCI (1<<1)
> -#define VME_DMA_VME (1<<2)
> -
> -#define VME_DMA_PATTERN_BYTE (1<<0)
> -#define VME_DMA_PATTERN_WORD (1<<1)
> -#define VME_DMA_PATTERN_INCREMENT (1<<2)
> -
> -#define VME_DMA_VME_TO_MEM (1<<0)
> -#define VME_DMA_MEM_TO_VME (1<<1)
> -#define VME_DMA_VME_TO_VME (1<<2)
> -#define VME_DMA_MEM_TO_MEM (1<<3)
> -#define VME_DMA_PATTERN_TO_VME (1<<4)
> -#define VME_DMA_PATTERN_TO_MEM (1<<5)
> +#define VME_DMA_PATTERN (1 << 0)
> +#define VME_DMA_PCI (1 << 1)
> +#define VME_DMA_VME (1 << 2)
> +
> +#define VME_DMA_PATTERN_BYTE (1 << 0)
> +#define VME_DMA_PATTERN_WORD (1 << 1)
> +#define VME_DMA_PATTERN_INCREMENT (1 << 2)
> +
> +#define VME_DMA_VME_TO_MEM (1 << 0)
> +#define VME_DMA_MEM_TO_VME (1 << 1)
> +#define VME_DMA_VME_TO_VME (1 << 2)
> +#define VME_DMA_MEM_TO_MEM (1 << 3)
> +#define VME_DMA_PATTERN_TO_VME (1 << 4)
> +#define VME_DMA_PATTERN_TO_MEM (1 << 5)
>
> struct vme_dma_attr {
> u32 type;
I propose to use the BIT macro as checkpatch proposes it when I apply
checkpatch to your patch. Please also correct the number of tabs to align.
Thanks,
Bye Philipp
CHECK: Prefer using the BIT macro
#37: FILE: drivers/staging/vme_user/vme.h:57:
+#define VME_DMA_PATTERN (1 << 0)
prev parent reply other threads:[~2022-12-14 7:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 19:55 Abhirup Deb
2022-12-14 7:00 ` Philipp Hortmann [this message]
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=c1887a83-25c2-0979-e790-04cdd5ad4aec@gmail.com \
--to=philipp.g.hortmann@gmail.com \
--cc=abhirupdeb@linux.vnet.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=manohar.vanga@gmail.com \
--cc=martyn@welchs.me.uk \
/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
all inboxes | Powered by JetHome®