From: Nicola Vetrini <nicola.vetrini@bugseng.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: sstabellini@kernel.org, michal.orzel@amd.com,
xenia.ragiadakou@amd.com, ayan.kumar.halder@amd.com,
consulting@bugseng.com, andrew.cooper3@citrix.com,
roger.pau@citrix.com, bertrand.marquis@arm.com, julien@xen.org,
George Dunlap <george.dunlap@citrix.com>, Wei Liu <wl@xen.org>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
xen-devel@lists.xenproject.org
Subject: Re: [XEN PATCH v3] xen: replace occurrences of SAF-1-safe with asmlinkage attribute
Date: Thu, 23 Nov 2023 12:30:37 +0100 [thread overview]
Message-ID: <6d89d2e3cb2ac28f7f40285f213c74ef@bugseng.com> (raw)
In-Reply-To: <23575a74-2a8d-41d3-a71a-420f6a6007c8@suse.com>
I guess this one as well should remain as is. Can you confirm?
void asmlinkage __stdcall cmdline_parse_early(const char *cmdline,
early_boot_opts_t *ebo)
--
Nicola Vetrini, BSc
Software Engineer, BUGSENG srl (https://bugseng.com)
next prev parent reply other threads:[~2023-11-23 11:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 9:08 [XEN PATCH v3] xen: replace occurrences of SAF-1-safe with asmlinkage attribute Nicola Vetrini
2023-11-16 9:15 ` Nicola Vetrini
2023-11-17 19:15 ` Julien Grall
2023-11-18 2:47 ` Stefano Stabellini
2023-11-20 10:22 ` Julien Grall
2023-11-20 8:39 ` Nicola Vetrini
2023-11-20 8:46 ` Jan Beulich
2023-11-20 10:27 ` Julien Grall
2023-11-21 8:16 ` Nicola Vetrini
2023-11-21 9:16 ` Jan Beulich
2023-11-21 9:46 ` Nicola Vetrini
2023-11-21 10:18 ` Jan Beulich
2023-11-21 10:31 ` Nicola Vetrini
2023-11-23 8:57 ` Jan Beulich
2023-11-23 9:25 ` Nicola Vetrini
2023-11-23 10:26 ` Julien Grall
2023-11-23 10:31 ` Jan Beulich
2023-11-23 10:40 ` Nicola Vetrini
2023-11-23 10:43 ` Julien Grall
2023-11-23 11:30 ` Nicola Vetrini [this message]
2023-11-23 11:36 ` Jan Beulich
2023-11-23 11:39 ` Nicola Vetrini
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=6d89d2e3cb2ac28f7f40285f213c74ef@bugseng.com \
--to=nicola.vetrini@bugseng.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=ayan.kumar.halder@amd.com \
--cc=bertrand.marquis@arm.com \
--cc=consulting@bugseng.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.org \
--cc=xenia.ragiadakou@amd.com \
/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.