All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Cochran <richardcochran@gmail.com>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org,
	Julia Lawall <julia.lawall@lip6.fr>
Subject: Re: posix-clock: Use an unsigned data type for a variable
Date: Mon, 21 Dec 2015 10:12:36 +0000	[thread overview]
Message-ID: <20151221101236.GA4285@localhost.localdomain> (raw)
In-Reply-To: <5677C6B3.8060007@users.sourceforge.net>

On Mon, Dec 21, 2015 at 10:30:27AM +0100, SF Markus Elfring wrote:
> > In this case, there is indeed a problem.  However, just changing the
> > type won't fix it.
> 
> Would you like to explain your view on the handling of potential
> data type mismatches a bit more?

Yes, I will explain in the patch that follows.

Thanks,
Richard

WARNING: multiple messages have this Message-ID (diff)
From: Richard Cochran <richardcochran@gmail.com>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org,
	Julia Lawall <julia.lawall@lip6.fr>
Subject: Re: posix-clock: Use an unsigned data type for a variable
Date: Mon, 21 Dec 2015 11:12:36 +0100	[thread overview]
Message-ID: <20151221101236.GA4285@localhost.localdomain> (raw)
In-Reply-To: <5677C6B3.8060007@users.sourceforge.net>

On Mon, Dec 21, 2015 at 10:30:27AM +0100, SF Markus Elfring wrote:
> > In this case, there is indeed a problem.  However, just changing the
> > type won't fix it.
> 
> Would you like to explain your view on the handling of potential
> data type mismatches a bit more?

Yes, I will explain in the patch that follows.

Thanks,
Richard

  reply	other threads:[~2015-12-21 10:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-20  8:19 [PATCH] posix-clock: Use an unsigned data type for a variable SF Markus Elfring
2015-12-20  8:19 ` SF Markus Elfring
2015-12-20 11:09 ` Julia Lawall
2015-12-20 11:09   ` Julia Lawall
2015-12-20 12:48   ` SF Markus Elfring
2015-12-20 12:48     ` SF Markus Elfring
2015-12-20 12:51     ` Julia Lawall
2015-12-20 12:51       ` Julia Lawall
2015-12-20 13:08       ` SF Markus Elfring
2015-12-20 13:08         ` SF Markus Elfring
2015-12-20 20:09 ` Richard Cochran
2015-12-20 20:09   ` Richard Cochran
2015-12-21  9:30   ` SF Markus Elfring
2015-12-21  9:30     ` SF Markus Elfring
2015-12-21 10:12     ` Richard Cochran [this message]
2015-12-21 10:12       ` Richard Cochran
2015-12-22 21:19 ` [PATCH] posix-clock: fix return code on the poll method's error path Richard Cochran
2015-12-22 21:19   ` Richard Cochran
2015-12-29 10:36   ` [tip:timers/urgent] posix-clock: Fix " tip-bot for Richard Cochran

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=20151221101236.GA4285@localhost.localdomain \
    --to=richardcochran@gmail.com \
    --cc=elfring@users.sourceforge.net \
    --cc=julia.lawall@lip6.fr \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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.