From: Federico Serafini <federico.serafini@bugseng.com>
To: xen-devel@lists.xenproject.org
Cc: consulting@bugseng.com,
"Federico Serafini" <federico.serafini@bugseng.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>, "Wei Liu" <wl@xen.org>
Subject: [XEN PATCH 3/8] x86/vpmu: address a violation of MISRA C:2012 Rule 8.2
Date: Mon, 23 Oct 2023 09:22:58 +0200 [thread overview]
Message-ID: <064278aecf69859c664784ba18a7189d885112c0.1698045505.git.federico.serafini@bugseng.com> (raw)
In-Reply-To: <cover.1698045505.git.federico.serafini@bugseng.com>
Add missing parameter name. No functional change.
Signed-off-by: Federico Serafini <federico.serafini@bugseng.com>
---
xen/arch/x86/include/asm/vpmu.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/xen/arch/x86/include/asm/vpmu.h b/xen/arch/x86/include/asm/vpmu.h
index b165acc6c2..7858aec6ca 100644
--- a/xen/arch/x86/include/asm/vpmu.h
+++ b/xen/arch/x86/include/asm/vpmu.h
@@ -35,7 +35,7 @@ struct arch_vpmu_ops {
void (*arch_vpmu_destroy)(struct vcpu *v);
int (*arch_vpmu_save)(struct vcpu *v, bool_t to_guest);
int (*arch_vpmu_load)(struct vcpu *v, bool_t from_guest);
- void (*arch_vpmu_dump)(const struct vcpu *);
+ void (*arch_vpmu_dump)(const struct vcpu *v);
#ifdef CONFIG_MEM_SHARING
int (*allocate_context)(struct vcpu *v);
--
2.34.1
next prev parent reply other threads:[~2023-10-23 7:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 7:22 [XEN PATCH 0/8] x86: address some violations of MISRA C:2012 Rule 8.2 Federico Serafini
2023-10-23 7:22 ` [XEN PATCH 1/8] x86/hvm: address " Federico Serafini
2023-10-30 15:56 ` Jan Beulich
2023-10-23 7:22 ` [XEN PATCH 2/8] x86/mmconfig: " Federico Serafini
2023-10-30 15:57 ` Jan Beulich
2023-10-23 7:22 ` Federico Serafini [this message]
2023-10-30 15:57 ` [XEN PATCH 3/8] x86/vpmu: address a violation " Jan Beulich
2023-10-23 7:22 ` [XEN PATCH 4/8] x86/smp: " Federico Serafini
2023-10-30 15:58 ` Jan Beulich
2023-10-23 7:23 ` [XEN PATCH 5/8] x86/pci: " Federico Serafini
2023-10-30 15:58 ` Jan Beulich
2023-10-23 7:23 ` [XEN PATCH 6/8] x86/physdev: address violations " Federico Serafini
2023-10-30 16:01 ` Jan Beulich
2023-10-23 7:23 ` [XEN PATCH 7/8] x86/platform_hypercall: " Federico Serafini
2023-10-30 16:06 ` Jan Beulich
2023-10-23 7:23 ` [XEN PATCH 8/8] x86/sysctl: address a violation " Federico Serafini
2023-10-30 16:07 ` Jan Beulich
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=064278aecf69859c664784ba18a7189d885112c0.1698045505.git.federico.serafini@bugseng.com \
--to=federico.serafini@bugseng.com \
--cc=andrew.cooper3@citrix.com \
--cc=consulting@bugseng.com \
--cc=jbeulich@suse.com \
--cc=roger.pau@citrix.com \
--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.