All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Orzel <michal.orzel@arm.com>
To: xen-devel@lists.xenproject.org
Cc: 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: [PATCH 2/7] xen/domain: Use unsigned int instead of plain unsigned
Date: Mon, 27 Jun 2022 15:15:38 +0200	[thread overview]
Message-ID: <20220627131543.410971-3-michal.orzel@arm.com> (raw)
In-Reply-To: <20220627131543.410971-1-michal.orzel@arm.com>

This is just for the style and consistency reasons as the former is
being used more often than the latter.

Signed-off-by: Michal Orzel <michal.orzel@arm.com>
---
 xen/common/domain.c      | 2 +-
 xen/include/xen/domain.h | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/xen/common/domain.c b/xen/common/domain.c
index 7570eae91a..57a8515f21 100644
--- a/xen/common/domain.c
+++ b/xen/common/domain.c
@@ -1446,7 +1446,7 @@ int vcpu_reset(struct vcpu *v)
  * of memory, and it sets a pending event to make sure that a pending
  * event doesn't get missed.
  */
-int map_vcpu_info(struct vcpu *v, unsigned long gfn, unsigned offset)
+int map_vcpu_info(struct vcpu *v, unsigned long gfn, unsigned int offset)
 {
     struct domain *d = v->domain;
     void *mapping;
diff --git a/xen/include/xen/domain.h b/xen/include/xen/domain.h
index 1c3c88a14d..628b14b086 100644
--- a/xen/include/xen/domain.h
+++ b/xen/include/xen/domain.h
@@ -65,7 +65,7 @@ void cf_check free_pirq_struct(void *);
 int  arch_vcpu_create(struct vcpu *v);
 void arch_vcpu_destroy(struct vcpu *v);
 
-int map_vcpu_info(struct vcpu *v, unsigned long gfn, unsigned offset);
+int map_vcpu_info(struct vcpu *v, unsigned long gfn, unsigned int offset);
 void unmap_vcpu_info(struct vcpu *v);
 
 int arch_domain_create(struct domain *d,
-- 
2.25.1



  parent reply	other threads:[~2022-06-27 13:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-27 13:15 [PATCH 0/7] xen/arm: use unsigned int instead of plain unsigned Michal Orzel
2022-06-27 13:15 ` [PATCH 1/7] xen/arm: Use " Michal Orzel
2022-06-27 13:25   ` Julien Grall
2022-06-27 13:15 ` Michal Orzel [this message]
2022-06-27 13:22   ` [PATCH 2/7] xen/domain: " Jan Beulich
2022-06-27 13:15 ` [PATCH 3/7] xen/common: " Michal Orzel
2022-06-27 13:22   ` Jan Beulich
2022-06-27 14:13   ` Juergen Gross
2022-06-29 10:46   ` Michal Orzel
2022-06-29 10:52     ` Julien Grall
2022-07-05 12:07       ` Bertrand Marquis
2022-07-05 12:50         ` Julien Grall
2022-06-27 13:15 ` [PATCH 4/7] include/xen: " Michal Orzel
2022-06-27 13:23   ` Jan Beulich
2022-06-27 13:15 ` [PATCH 5/7] include/public: Use uint32_t instead of unsigned (int) Michal Orzel
2022-06-27 13:24   ` Jan Beulich
2022-06-27 13:15 ` [PATCH 6/7] xsm/flask: Use unsigned int instead of plain unsigned Michal Orzel
2022-06-27 13:26   ` Jan Beulich
2022-06-27 19:19   ` Daniel P. Smith
2022-06-28  6:28     ` Michal Orzel
2022-06-27 13:15 ` [PATCH 7/7] drivers/acpi: Drop the unneeded casts to unsigned Michal Orzel
2022-06-27 13:27   ` 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=20220627131543.410971-3-michal.orzel@arm.com \
    --to=michal.orzel@arm.com \
    --cc=andrew.cooper3@citrix.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.