Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757139AbbBEMXS (ORCPT ); Thu, 5 Feb 2015 07:23:18 -0500 Received: from ns.mm-sol.com ([37.157.136.199]:44045 "EHLO extserv.mm-sol.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752067AbbBEMXQ (ORCPT ); Thu, 5 Feb 2015 07:23:16 -0500 Message-ID: <1423138991.6471.9.camel@mm-sol.com> Subject: Re: [PATCH 2/3] iio: qcom-spmi-iadc: cleanup wait_for_completion return handling From: "Ivan T. Ivanov" To: Jonathan Cameron Cc: Nicholas Mc Guire , Hartmut Knaack , Lars-Peter Clausen , Peter Meerwald , linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org Date: Thu, 05 Feb 2015 14:23:11 +0200 In-Reply-To: <54D24FDE.7000908@kernel.org> References: <1422866227-10484-1-git-send-email-hofrat@osadl.org> <54D24FDE.7000908@kernel.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.13.7-fta1.2~trusty Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1058 Lines: 27 On Wed, 2015-02-04 at 16:59 +0000, Jonathan Cameron wrote: > On 02/02/15 08:37, Nicholas Mc Guire wrote: > > This patch fixes two issues: > > * return type of wait_for_completion_timeout is unsigned long not int, > > rather than adding a dedicated variable the wait_for_completion_timeout > > is moved into the condition directly > > * the timeout of wait_for_completion_timeout is in jiffies but the value > > being passed was a unsigned long not converted to jiffies and thus was > > dependent on the HZ settings which is probably not what you want. > > > > Signed-off-by: Nicholas Mc Guire > Ivan, need your Ack / Reviewed-by on this one. > Yes, change is correct, as explained before [1]. Acked-by: Ivan T. Ivanov [1] https://lkml.org/lkml/2015/1/5/409 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/