From: chenguohua@jari.cn
To: tzimmermann@suse.de
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: [PATCH] iosys-map: Clean up errors in iosys-map.h
Date: Fri, 13 Oct 2023 10:58:14 +0800 (GMT+08:00) [thread overview]
Message-ID: <14ac9e76.941.18b26f86290.Coremail.chenguohua@jari.cn> (raw)
Fix the following errors reported by checkpatch:
ERROR: spaces required around that ':' (ctx:VxW)
Signed-off-by: GuoHua Cheng <chenguohua@jari.cn>
---
include/linux/iosys-map.h | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/include/linux/iosys-map.h b/include/linux/iosys-map.h
index cb71aa616bd3..108fd0dd9121 100644
--- a/include/linux/iosys-map.h
+++ b/include/linux/iosys-map.h
@@ -349,29 +349,29 @@ static inline void iosys_map_memset(struct iosys_map *dst, size_t offset,
#ifdef CONFIG_64BIT
#define __iosys_map_rd_io_u64_case(val_, vaddr_iomem_) \
- u64: val_ = readq(vaddr_iomem_)
+ u64 : val_ = readq(vaddr_iomem_)
#define __iosys_map_wr_io_u64_case(val_, vaddr_iomem_) \
- u64: writeq(val_, vaddr_iomem_)
+ u64 : writeq(val_, vaddr_iomem_)
#else
#define __iosys_map_rd_io_u64_case(val_, vaddr_iomem_) \
- u64: memcpy_fromio(&(val_), vaddr_iomem_, sizeof(u64))
+ u64 : memcpy_fromio(&(val_), vaddr_iomem_, sizeof(u64))
#define __iosys_map_wr_io_u64_case(val_, vaddr_iomem_) \
- u64: memcpy_toio(vaddr_iomem_, &(val_), sizeof(u64))
+ u64 : memcpy_toio(vaddr_iomem_, &(val_), sizeof(u64))
#endif
#define __iosys_map_rd_io(val__, vaddr_iomem__, type__) _Generic(val__, \
- u8: val__ = readb(vaddr_iomem__), \
- u16: val__ = readw(vaddr_iomem__), \
- u32: val__ = readl(vaddr_iomem__), \
+ u8 : val__ = readb(vaddr_iomem__), \
+ u16 : val__ = readw(vaddr_iomem__), \
+ u32 : val__ = readl(vaddr_iomem__), \
__iosys_map_rd_io_u64_case(val__, vaddr_iomem__))
#define __iosys_map_rd_sys(val__, vaddr__, type__) \
val__ = READ_ONCE(*(type__ *)(vaddr__))
#define __iosys_map_wr_io(val__, vaddr_iomem__, type__) _Generic(val__, \
- u8: writeb(val__, vaddr_iomem__), \
- u16: writew(val__, vaddr_iomem__), \
- u32: writel(val__, vaddr_iomem__), \
+ u8 : writeb(val__, vaddr_iomem__), \
+ u16 : writew(val__, vaddr_iomem__), \
+ u32 : writel(val__, vaddr_iomem__), \
__iosys_map_wr_io_u64_case(val__, vaddr_iomem__))
#define __iosys_map_wr_sys(val__, vaddr__, type__) \
--
2.17.1
next reply other threads:[~2023-10-13 2:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 2:58 chenguohua [this message]
2023-10-13 6:56 ` Thomas Zimmermann
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=14ac9e76.941.18b26f86290.Coremail.chenguohua@jari.cn \
--to=chenguohua@jari.cn \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tzimmermann@suse.de \
/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®