Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752671AbbHMMZf (ORCPT ); Thu, 13 Aug 2015 08:25:35 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:54367 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751559AbbHMMZe (ORCPT ); Thu, 13 Aug 2015 08:25:34 -0400 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: ath9k_htc: match wait_for_completion_timeout return type From: Kalle Valo In-Reply-To: <1431617394-30725-1-git-send-email-hofrat@osadl.org> To: Nicholas Mc Guire Cc: QCA ath9k Development , linux-wireless@vger.kernel.org, ath9k-devel@venema.h4ckr.net, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, Nicholas Mc Guire Message-Id: <20150813122533.52E091402D5@smtp.codeaurora.org> Date: Thu, 13 Aug 2015 12:25:33 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1109 Lines: 30 > Return type of wait_for_completion_timeout is unsigned long not int. > As time_left is exclusively used for wait_for_completion_timeout here its > type is simply changed to unsigned long. > > API conformance testing for completions with coccinelle spatches are being > used to locate API usage inconsistencies: > ./drivers/net/wireless/ath/ath9k/htc_hst.c:171 > int return assigned to unsigned long > ./drivers/net/wireless/ath/ath9k/htc_hst.c:277 > int return assigned to unsigned long > ./drivers/net/wireless/ath/ath9k/htc_hst.c:206 > int return assigned to unsigned long > > Patch was compile tested with x86_64_defconfig + CONFIG_ATH_CARDS=m, > CONFIG_ATH9K_HTC=m > > Patch is against 4.1-rc3 (localversion-next is -next-20150514) > > > Signed-off-by: Nicholas Mc Guire Thanks, applied to wireless-drivers-next.git. Kalle Valo -- 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/