From: Jan Beulich <jbeulich@suse.com>
To: Nicola Vetrini <nicola.vetrini@bugseng.com>
Cc: xen-devel@lists.xenproject.org, consulting@bugseng.com,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>, "Wei Liu" <wl@xen.org>,
"Stefano Stabellini" <sstabellini@kernel.org>
Subject: Re: [XEN PATCH v3 1/3] xen/x86: add missing instances of asmlinkage attributes
Date: Mon, 18 Dec 2023 15:03:04 +0100 [thread overview]
Message-ID: <ffa5a22a-36cf-4817-aae3-668d6ff181bf@suse.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2312111748300.1703076@ubuntu-linux-20-04-desktop>
On 12.12.2023 02:48, Stefano Stabellini wrote:
> On Mon, 11 Dec 2023, Nicola Vetrini wrote:
>> No functional change.
>>
>> Signed-off-by: Nicola Vetrini <nicola.vetrini@bugseng.com>
>
> Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
Acked-by: Jan Beulich <jbeulich@suse.com>
next prev parent reply other threads:[~2023-12-18 14:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 9:14 [XEN PATCH v3 0/3] address some violations of MISRA C Rule 8.4 Nicola Vetrini
2023-12-11 9:14 ` [XEN PATCH v3 1/3] xen/x86: add missing instances of asmlinkage attributes Nicola Vetrini
2023-12-12 1:48 ` Stefano Stabellini
2023-12-18 14:03 ` Jan Beulich [this message]
2023-12-11 9:14 ` [XEN PATCH v3 2/3] x86/viridian: make build_assertions static Nicola Vetrini
2023-12-11 9:15 ` Durrant, Paul
2023-12-11 9:14 ` [XEN PATCH v3 3/3] xen/mm: add declaration for first_valid_mfn Nicola Vetrini
2023-12-12 23:24 ` Stefano Stabellini
2023-12-13 8:26 ` Jan Beulich
2023-12-14 2:05 ` Stefano Stabellini
2023-12-14 7:53 ` Jan Beulich
2023-12-14 8:32 ` Julien Grall
2023-12-14 8:51 ` Jan Beulich
2023-12-14 14:15 ` George Dunlap
2023-12-14 19:10 ` Julien Grall
2023-12-14 21:27 ` Stefano Stabellini
2023-12-15 8:03 ` Jan Beulich
2023-12-15 9:43 ` Julien Grall
2023-12-15 9:59 ` Nicola Vetrini
2023-12-15 10:06 ` Julien Grall
2023-12-15 21:01 ` Stefano Stabellini
2023-12-14 8:49 ` 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=ffa5a22a-36cf-4817-aae3-668d6ff181bf@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=consulting@bugseng.com \
--cc=nicola.vetrini@bugseng.com \
--cc=roger.pau@citrix.com \
--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.