From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751314AbbLUKMn (ORCPT ); Mon, 21 Dec 2015 05:12:43 -0500 Received: from mail-wm0-f47.google.com ([74.125.82.47]:36141 "EHLO mail-wm0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751074AbbLUKMl (ORCPT ); Mon, 21 Dec 2015 05:12:41 -0500 Date: Mon, 21 Dec 2015 11:12:36 +0100 From: Richard Cochran To: SF Markus Elfring Cc: LKML , kernel-janitors@vger.kernel.org, Julia Lawall Subject: Re: posix-clock: Use an unsigned data type for a variable Message-ID: <20151221101236.GA4285@localhost.localdomain> References: <56766488.9050402@users.sourceforge.net> <20151220200934.GB2027@netboy> <5677C6B3.8060007@users.sourceforge.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5677C6B3.8060007@users.sourceforge.net> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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