All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: Jan Beulich <JBeulich@suse.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] APEI: pull a signedness check ahead for Coverity's sake
Date: Thu, 9 Jun 2016 15:24:11 +0100	[thread overview]
Message-ID: <57597C0B.1080308@arm.com> (raw)
In-Reply-To: <57581F9802000078000F2FD6@prv-mh.provo.novell.com>

Hi Jan,

On 08/06/16 12:37, Jan Beulich wrote:
> On 64-bit architectures (which is all we care about right now in ACPI
> code), the value coming from a __u32 field makes "len" positive anyway,
> but since from an abstract pov the tool is right, let's just re-order
> things.

All the usage of len are unsigned, so why do we want to keep len signed?

Regards,

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  parent reply	other threads:[~2016-06-09 14:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-08 11:37 [PATCH] APEI: pull a signedness check ahead for Coverity's sake Jan Beulich
2016-06-09 14:13 ` Andrew Cooper
2016-06-09 14:24 ` Julien Grall [this message]
2016-06-09 15:08   ` 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=57597C0B.1080308@arm.com \
    --to=julien.grall@arm.com \
    --cc=JBeulich@suse.com \
    --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.