All of lore.kernel.org
 help / color / mirror / Atom feed
From: Federico Serafini <federico.serafini@bugseng.com>
To: xen-devel@lists.xenproject.org
Cc: consulting@bugseng.com,
	Federico Serafini <federico.serafini@bugseng.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	George Dunlap <george.dunlap@citrix.com>,
	Jan Beulich <jbeulich@suse.com>, Julien Grall <julien@xen.org>,
	Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>
Subject: [XEN PATCH 4/5] xen/vmap: address violations of MISRA C:2012 Rule 8.2
Date: Fri, 17 Nov 2023 09:40:08 +0100	[thread overview]
Message-ID: <d4d67e48298f4b51836c3c5b0a982775f469d74b.1700209834.git.federico.serafini@bugseng.com> (raw)
In-Reply-To: <cover.1700209834.git.federico.serafini@bugseng.com>

Add missing parameter names. No functional change.

Signed-off-by: Federico Serafini <federico.serafini@bugseng.com>
---
 xen/include/xen/vmap.h | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/xen/include/xen/vmap.h b/xen/include/xen/vmap.h
index b0f7632e89..2b7369e062 100644
--- a/xen/include/xen/vmap.h
+++ b/xen/include/xen/vmap.h
@@ -13,9 +13,9 @@ enum vmap_region {
 void vm_init_type(enum vmap_region type, void *start, void *end);
 
 void *__vmap(const mfn_t *mfn, unsigned int granularity, unsigned int nr,
-             unsigned int align, unsigned int flags, enum vmap_region);
+             unsigned int align, unsigned int flags, enum vmap_region type);
 void *vmap(const mfn_t *mfn, unsigned int nr);
-void vunmap(const void *);
+void vunmap(const void *va);
 
 void *vmalloc(size_t size);
 void *vmalloc_xen(size_t size);
@@ -23,7 +23,7 @@ void *vmalloc_xen(size_t size);
 void *vzalloc(size_t size);
 void vfree(void *va);
 
-void __iomem *ioremap(paddr_t, size_t);
+void __iomem *ioremap(paddr_t pa, size_t len);
 
 static inline void iounmap(void __iomem *va)
 {
-- 
2.34.1



  parent reply	other threads:[~2023-11-17  8:40 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-17  8:40 [XEN PATCH 0/5] xen: address some violations of MISRA C:2012 Rule 8.2 Federico Serafini
2023-11-17  8:40 ` [XEN PATCH 1/5] xen/common: address " Federico Serafini
2023-11-18  2:59   ` Stefano Stabellini
2023-11-20 13:55     ` Federico Serafini
2023-11-21  0:02       ` Stefano Stabellini
2023-11-23  8:59         ` Jan Beulich
2023-11-17  8:40 ` [XEN PATCH 2/5] xen/serial: " Federico Serafini
2023-11-18  3:02   ` Stefano Stabellini
2023-11-17  8:40 ` [XEN PATCH 3/5] xen/sort: " Federico Serafini
2023-11-18  3:05   ` Stefano Stabellini
2023-11-20  9:02   ` Jan Beulich
2023-11-20 13:13     ` Federico Serafini
2023-11-20 16:00       ` Jan Beulich
2023-11-21  0:04         ` Stefano Stabellini
2023-11-21  7:33           ` Jan Beulich
2023-11-22  1:19             ` Stefano Stabellini
2023-11-22  8:01               ` Jan Beulich
2023-11-22 10:05                 ` Federico Serafini
2023-11-17  8:40 ` Federico Serafini [this message]
2023-11-18  3:06   ` [XEN PATCH 4/5] xen/vmap: " Stefano Stabellini
2023-11-17  8:40 ` [XEN PATCH 5/5] xen/xalloc: " Federico Serafini
2023-11-18  3:06   ` Stefano Stabellini

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=d4d67e48298f4b51836c3c5b0a982775f469d74b.1700209834.git.federico.serafini@bugseng.com \
    --to=federico.serafini@bugseng.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=consulting@bugseng.com \
    --cc=george.dunlap@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=sstabellini@kernel.org \
    --cc=wl@xen.org \
    --cc=xen-devel@lists.xenproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.