linux-kernel - Re: [PATCH 1/2 v2] Documentation, split up rtc.txt into documentation and test file

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 for Android: free password hash cracker in your pocket

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

Date:	Tue, 24 Mar 2015 22:25:11 -0600
From:	Shuah Khan <shuahkh@....samsung.com>
To:	Prarit Bhargava <prarit@...hat.com>, linux-kernel@...r.kernel.org
CC:	corbet@....net, rtc-linux@...glegroups.com,
	linux-doc@...r.kernel.org, a.zummo@...ertech.it,
	john.stultz@...aro.org
Subject: Re: [PATCH 1/2 v2] Documentation, split up rtc.txt into documentation
 and test file

On 03/23/2015 02:32 PM, Prarit Bhargava wrote:
> This patch splits rtc.txt into two separate files, one for the
> documentation itself, and the other for the rtctest.c file.  The rtctest
> file is moved into the kernel tools/testing/selftests/timers directory.
> This will make automated testing easier.  Note that the only difference in
> the rtc.txt file is that the location of the rtctest.c file has changed.
> 
> Signed-off-by: Prarit Bhargava <prarit@...hat.com>
> Cc: corbet@....net
> Cc: rtc-linux@...glegroups.com
> Cc: linux-doc@...r.kernel.org
> Cc: a.zummo@...ertech.it
> Cc: prarit@...hat.com
> Cc: john.stultz@...aro.org
> Cc: shuahkh@....samsung.com
> 

Applied this patch and 2/2 to linux-kselftest next for 4.1

thanks,
-- Shuah

-- 
Shuah Khan
Sr. Linux Kernel Developer
Open Source Innovation Group
Samsung Research America (Silicon Valley)
shuahkh@....samsung.com | (970) 217-8978
--
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/