From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D250FDF6C for ; Sun, 22 Feb 2026 11:11:23 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.198.163.8 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771758684; cv=none; b=rttWvkuGfxJPWUysgdH7PmvaOTa/PGwP1AEad9p0ulRYCcPEn30L9grNfHfEkPgcBcKHzs3AVeRjOwYz+8i/zKRH4Osv5cRVdDnT9aagTLWJGrSz22CQKlfZ72PfErjDywJJbUemsmaPwWp1ibk/tdUiGnCWPCxiOk0fIovFs58= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771758684; c=relaxed/simple; bh=EzBXikAhpFgSG9WkHqDkREPdenROlKQQO9Y2tXQJgRM=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=LWaQGQYnvXJGk64AhJvFsuTaCeQFjuD3MMgnCOpGQdYYS22wyCdgTTmoBX9zPaiRwtSeA4LRwDjfxE9zgj+vEDmGqAouvBrP/TnPDPrTrWj/bRnblxqEPh3MxYL0j3ugl2UM/iKMIUjlCoi8veV7aHgf5iPYmXizETnzbXOdOys= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=intel.com; spf=pass smtp.mailfrom=intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=jnklb0H4; arc=none smtp.client-ip=192.198.163.8 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="jnklb0H4" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1771758684; x=1803294684; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=EzBXikAhpFgSG9WkHqDkREPdenROlKQQO9Y2tXQJgRM=; b=jnklb0H4i8Y2tyh0oemZVyAs4m6nJU6wgioo9qUD0rTrKKLEcvMBw/AQ Q272c8yqS7cHooKZM/FUCJe4LcwSZDpD70oPpEDdI0+craqiP4Rp4xd+Q Mkk8khTpmy+oBPTtpfgXn2J+6VLw8YxDnB7qbk3YpGRGJ8jQxWfPn6wLT FSGHAWm8ymlSK09S+QfVpyYuRSS5bRYJPxngjWDxoqJmZc1W1EQ3CO9vk xBhSEvkaoAWZjUIsVG25b2eacwBkPLwBxXBuX56X+NYrP4+6ytQx1MIE9 D8rP9c//YNzylCZrTiUQSzNaXZaHLXCuUc3xMg3pALlnnJZbk+DdD95b7 A==; X-CSE-ConnectionGUID: zfq7nJXJQ9yPG3P+UMxJSw== X-CSE-MsgGUID: 6+Jjp2VuSQyVNabm1keTuw== X-IronPort-AV: E=McAfee;i="6800,10657,11708"; a="90364556" X-IronPort-AV: E=Sophos;i="6.21,304,1763452800"; d="scan'208";a="90364556" Received: from fmviesa003.fm.intel.com ([10.60.135.143]) by fmvoesa102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 22 Feb 2026 03:11:23 -0800 X-CSE-ConnectionGUID: PBhVUIJeTya70dfTBUIGWg== X-CSE-MsgGUID: V2QOP6NXStCYCqyduRrtsg== X-ExtLoop1: 1 Received: from dhhellew-desk2.ger.corp.intel.com (HELO localhost) ([10.245.245.171]) by fmviesa003-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 22 Feb 2026 03:11:21 -0800 Date: Sun, 22 Feb 2026 13:11:19 +0200 From: Andy Shevchenko To: Neel Bullywon Cc: apw@canonical.com, joe@perches.com, dwaipayanray1@gmail.com, lukas.bulwahn@gmail.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2] checkpatch: mention fsleep() in MSLEEP and USLEEP_RANGE warnings Message-ID: References: <20260220230555.56255-1-neelb2403@gmail.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260220230555.56255-1-neelb2403@gmail.com> Organization: Intel Finland Oy - BIC 0357606-4 - c/o Alberga Business Park, 6 krs, Bertel Jungin Aukio 5, 02600 Espoo On Fri, Feb 20, 2026 at 06:05:55PM -0500, Neel Bullywon wrote: > Expand the MSLEEP warning to also reference fsleep() alongside > msleep(), and expand the USLEEP_RANGE check to reference fsleep() > alongside usleep_range() and udelay(). fsleep() autoselects the > best sleep mechanism based on duration, making it a useful > alternative for developers to consider. ... > - "usleep_range is preferred over udelay; see function description of usleep_range() and udelay().\n" . $herecurr); > + "usleep_range is preferred over udelay; see function description of usleep_range(), udelay(), and fsleep().\n" . $herecurr); "fsleep() is preferred over others; usleep_range() is preferred over udelay(); see function descriptions of usleep_range(), udelay(), and fsleep().\n" ... > - "msleep < 20ms can sleep for up to 20ms; see function description of msleep().\n" . $herecurr); > + "msleep < 20ms can sleep for up to 20ms; see function description of msleep() and fsleep().\n" . $herecurr); "msleep < 20ms can sleep for up to 20ms; consider using fsleep(); see function description of msleep() and fsleep().\n" -- With Best Regards, Andy Shevchenko