From: Jan Beulich <jbeulich@suse.com>
To: Michal Orzel <michal.orzel@arm.com>
Cc: Daniel De Graaf <dgdegra@tycho.nsa.gov>,
"Daniel P. Smith" <dpsmith@apertussolutions.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH 6/7] xsm/flask: Use unsigned int instead of plain unsigned
Date: Mon, 27 Jun 2022 15:26:14 +0200 [thread overview]
Message-ID: <7d71eda4-8695-83fd-d729-5c28070c1539@suse.com> (raw)
In-Reply-To: <20220627131543.410971-7-michal.orzel@arm.com>
On 27.06.2022 15:15, Michal Orzel wrote:
> 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>
Acked-by: Jan Beulich <jbeulich@suse.com>
next prev parent reply other threads:[~2022-06-27 13:26 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 ` [PATCH 2/7] xen/domain: " Michal Orzel
2022-06-27 13:22 ` 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 [this message]
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=7d71eda4-8695-83fd-d729-5c28070c1539@suse.com \
--to=jbeulich@suse.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=dpsmith@apertussolutions.com \
--cc=michal.orzel@arm.com \
--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.