All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Halil Pasic <pasic@linux.vnet.ibm.com>
Cc: Thomas Huth <thuth@redhat.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	qemu-s390x <qemu-s390x@nongnu.org>,
	Collin Walling <walling@linux.ibm.com>,
	Cornelia Huck <cohuck@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH for-2.13] pc-bios/s390-ccw: size_t should be unsigned
Date: Fri, 13 Apr 2018 16:40:15 +0100	[thread overview]
Message-ID: <CAFEAcA_2LLy5o4DnDw_7X-ZMKfvw=CXdADtH_DaGh3mNQSC50w@mail.gmail.com> (raw)
In-Reply-To: <df1a9534-c1ca-972b-91a6-359685a671df@linux.vnet.ibm.com>

On 13 April 2018 at 16:28, Halil Pasic <pasic@linux.vnet.ibm.com> wrote:
>
>
> On 04/13/2018 04:30 PM, Thomas Huth wrote:
>> "size_t" should be an unsigned type - the signed counterpart is called
>> "ssize_t" in the C standard instead. Thus we should also use this
>
> The first sentence sounds like ssize_t is too a type defined by some
> C standard. Is it or does ssize_t come form somewhere else? I find negative
> size a little difficult conceptually.

I think ssize_t is from POSIX:
http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/sys_types.h.html
"Used for a count of bytes or an error indication".

thanks
-- PMM

  reply	other threads:[~2018-04-13 15:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-13 14:30 [Qemu-devel] [PATCH for-2.13] pc-bios/s390-ccw: size_t should be unsigned Thomas Huth
2018-04-13 14:37 ` Philippe Mathieu-Daudé
2018-04-13 14:54 ` Collin Walling
2018-04-13 15:28 ` Halil Pasic
2018-04-13 15:40   ` Peter Maydell [this message]
2018-04-13 15:50   ` Thomas Huth
2018-04-13 16:59     ` Halil Pasic
2018-04-13 18:06       ` Philippe Mathieu-Daudé
2018-04-13 18:09         ` Collin Walling
2018-04-16  7:31           ` Cornelia Huck
2018-04-18 13:44       ` Eric Blake

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='CAFEAcA_2LLy5o4DnDw_7X-ZMKfvw=CXdADtH_DaGh3mNQSC50w@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=pasic@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=walling@linux.ibm.com \
    /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.