All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicola Vetrini <nicola.vetrini@bugseng.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: Julien Grall <julien@xen.org>, Jan Beulich <jbeulich@suse.com>,
	consulting@bugseng.com, Andrew Cooper <andrew.cooper3@citrix.com>,
	George Dunlap <george.dunlap@citrix.com>, Wei Liu <wl@xen.org>,
	xen-devel@lists.xenproject.org
Subject: Re: [XEN PATCH 2/2] xen/cpu: address MISRA C Rule 17.7
Date: Thu, 29 Feb 2024 10:56:22 +0100	[thread overview]
Message-ID: <ee30028d5c53f3b90acad005147b56f1@bugseng.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2402281437470.575685@ubuntu-linux-20-04-desktop>

On 2024-02-28 23:38, Stefano Stabellini wrote:
> On Wed, 28 Feb 2024, Julien Grall wrote:
>> Hi Nicola,
>> 
>> On 28/02/2024 11:09, Nicola Vetrini wrote:
>> > > I asked Roberto if void casts are an option for compliance.
>> > >
>> >
>> > void casts are an option for sure. The rationale for the rule explicitly
>> > lists them as a compliance mechanism. An interesting aspect is what would be
>> > the consensus around void casts on functions whose return value is always
>> > ignored vs. functions whose return value is sometimes ignored.
>> 
>> If a return is always ignored, then the function should return void. 
>> For the
>> second case, I think it will be on the case by case basis.
> 
> +1
> 

Ok, noted.

> 
>> > > In any case, I don't think we should use void casts in the specific
>> > > cases this patch is dealing with. Void casts (if anything) should be a
>> > > last resort while this patch fixes the issue in a better way.
>> 
>> +1.

-- 
Nicola Vetrini, BSc
Software Engineer, BUGSENG srl (https://bugseng.com)


  reply	other threads:[~2024-02-29  9:56 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
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 [this message]
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=ee30028d5c53f3b90acad005147b56f1@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.