linux-kernel - Re: [PATCH v2] staging: rts5208: use msecs_to

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20150125120122.GA14049@kroah.com>
Date:	Sun, 25 Jan 2015 20:01:22 +0800
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Nicholas Mc Guire <der.herr@...r.at>
Cc:	Surya Seetharaman <surya.seetharaman9@...il.com>,
	Keerthimai Janarthanan <keerthimaipb@...il.com>,
	Tina Johnson <tinajohnson.1234@...il.com>,
	Sarah Sharp <sarah.a.sharp@...ux.intel.com>,
	Fabio Falzoi <fabio.falzoi84@...il.com>,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] staging: rts5208: use msecs_to_jiffies for timeouts

On Fri, Jan 23, 2015 at 08:15:53AM +0100, Nicholas Mc Guire wrote:
> This is only an API consolidation and should make things more readable
> 
> Converting milliseconds to jiffies by val * HZ / 1000 is technically
> not wrong but msecs_to_jiffies(val) is the cleaner solution and handles
> corner cases correctly.
> 
> Signed-off-by: Nicholas Mc Guire <der.herr@...r.at>
> ---
> 
> v2: typo in patch subject fixed - no change in actual patch
> 
> This patch was only compile tested with x86_64_defconfig + CONFIG_STAGING=y, 
> CONFIG_RTS5208=m
> 
> Patch is against 3.19.0-rc5 -next-20150122
> 
>  drivers/staging/rts5208/rtsx_transport.c |   12 ++++++------
>  1 file changed, 6 insertions(+), 6 deletions(-)

Applied, thanks.

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/