From: Nicola Vetrini <nicola.vetrini@bugseng.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
xen-devel@lists.xenproject.org, consulting@bugseng.com,
Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
Julien Grall <julien@xen.org>, Wei Liu <wl@xen.org>
Subject: Re: [XEN PATCH 1/2] xen/console: drop return value from consoled_guest_rx/tx
Date: Mon, 26 Feb 2024 09:23:42 +0100 [thread overview]
Message-ID: <b417d7a330addd295b3cbbbac4bed2a4@bugseng.com> (raw)
In-Reply-To: <004877c8-9aea-44b9-aa93-65665b0d3a8d@suse.com>
On 2024-02-26 09:00, Jan Beulich wrote:
> On 23.02.2024 23:56, Stefano Stabellini wrote:
>> On Fri, 23 Feb 2024, Nicola Vetrini wrote:
>>> These functions never saw a usage of their return value since
>>> they were introduced, so it can be dropped since their usages
>>> violate MISRA C Rule 17.7:
>>> "The value returned by a function having non-void return type shall
>>> be used".
>>>
>>> No functional change.
>>>
>>> Signed-off-by: Nicola Vetrini <nicola.vetrini@bugseng.com>
>>
>> Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
>
> The cleanup is certainly okay, but would one of you mind clarifying in
> how
> far this code is relevant for certification? I don't expect there are
> plans
> to run shim Xen in any projected production uses for which
> certification is
> relevant? (The subject prefix is also unnecessarily wide here, when
> it's
> only daemon code which is affected, not console code in general.)
>
I agree on the subject prefix being too wide. The configuration that
uses consoled_guest_tx is #ifdef-ed for x86, so even in configurations
that may never reach this condition this is relevant, unless its #ifdef
is restricted to cases where the call may actually be reachable.
consoled_guest_rx was adjusted for uniformity, even though it's
technically not included in the configuration under analysis at the
moment.
--
Nicola Vetrini, BSc
Software Engineer, BUGSENG srl (https://bugseng.com)
next prev parent reply other threads:[~2024-02-26 8:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 9:35 [XEN PATCH 0/2] address some violations of MISRA C Rule 17.7 Nicola Vetrini
2024-02-23 9:35 ` [XEN PATCH 1/2] xen/console: drop return value from consoled_guest_rx/tx Nicola Vetrini
2024-02-23 22:56 ` Stefano Stabellini
2024-02-26 8:00 ` Jan Beulich
2024-02-26 8:23 ` Nicola Vetrini [this message]
2024-02-26 8:56 ` Jan Beulich
2024-02-26 22:49 ` Stefano Stabellini
2024-02-27 7:08 ` Jan Beulich
2024-02-28 2:01 ` Stefano Stabellini
2024-02-23 9:35 ` [XEN PATCH 2/2] xen/cpu: address MISRA C Rule 17.7 Nicola Vetrini
2024-02-23 22:58 ` Stefano Stabellini
2024-02-26 8:06 ` Jan Beulich
2024-02-27 0:26 ` Stefano Stabellini
2024-02-27 7:28 ` Jan Beulich
2024-02-27 11:52 ` Julien Grall
2024-02-27 12:47 ` Jan Beulich
2024-02-28 2:10 ` Stefano Stabellini
2024-02-28 11:09 ` Nicola Vetrini
2024-02-28 11:36 ` Julien Grall
2024-02-28 22:38 ` Stefano Stabellini
2024-02-29 9:56 ` Nicola Vetrini
2024-02-28 11:06 ` Nicola Vetrini
2024-02-28 11:22 ` 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=b417d7a330addd295b3cbbbac4bed2a4@bugseng.com \
--to=nicola.vetrini@bugseng.com \
--cc=andrew.cooper3@citrix.com \
--cc=consulting@bugseng.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.