From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Nicola Vetrini <nicola.vetrini@bugseng.com>
Cc: dmkhn@proton.me, xen-devel@lists.xenproject.org,
jbeulich@suse.com, roger.pau@citrix.com, consulting@bugseng.com,
dmukhin@ford.com, Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [PING MISRA] Re: [PATCH v5 2/2] x86/vmx: remove __vmread()
Date: Fri, 16 May 2025 13:54:24 +0100 [thread overview]
Message-ID: <c4edef18-e31b-465f-9618-21264088504f@citrix.com> (raw)
In-Reply-To: <da9e619607bcf85198505bde196fbc86@bugseng.com>
On 16/05/2025 1:53 pm, Nicola Vetrini wrote:
> On 2025-05-16 14:45, Andrew Cooper wrote:
>> Hello,
>>
>> This is adjusting some MISRA configuration. I'm reasonably sure the
>> change is fine as we're simply removing the referenced helper, but can
>> we get a second opinion from anyone who knows what
>> function-macro-properties.json is supposed to be doing?
>>
>> Thanks,
>>
>> ~Andrew
>>
>
> Hi Andrew,
>
> sorry, it slipped under other emails. The change is ok.
No worries. These things happen.
>
>> On 13/05/2025 6:28 am, dmkhn@proton.me wrote:
>>> From: Denis Mukhin <dmukhin@ford.com>
>>>
>>> Remove __vmread() and adjust ECLAIR configuration to account for the
>>> change.
>>>
>>> Signed-off-by: Denis Mukhin <dmukhin@ford.com>
>
> Reviewed-by: Nicola Vetrini <nicola.vetrini@bugseng.com>
Thankyou.
~Andrew
next prev parent reply other threads:[~2025-05-16 12:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 5:28 [PATCH v5 0/2] x86/vmx: __vmread() cleanup dmkhn
2025-05-13 5:28 ` [PATCH v5 1/2] x86/vmx: replace __vmread() with vmread() dmkhn
2025-05-16 12:42 ` Andrew Cooper
2025-05-16 17:41 ` dmkhn
2025-05-13 5:28 ` [PATCH v5 2/2] x86/vmx: remove __vmread() dmkhn
2025-05-16 12:45 ` [PING MISRA] " Andrew Cooper
2025-05-16 12:53 ` Nicola Vetrini
2025-05-16 12:54 ` Andrew Cooper [this message]
2025-05-16 18:07 ` dmkhn
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=c4edef18-e31b-465f-9618-21264088504f@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=consulting@bugseng.com \
--cc=dmkhn@proton.me \
--cc=dmukhin@ford.com \
--cc=jbeulich@suse.com \
--cc=nicola.vetrini@bugseng.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.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.