linux-kernel - Re: [PATCH v2.1] ftracetest: Do not use usleep directly

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <551D73D6.6030100@osg.samsung.com>
Date:	Thu, 02 Apr 2015 10:52:38 -0600
From:	Shuah Khan <shuahkh@....samsung.com>
To:	Steven Rostedt <rostedt@...dmis.org>
CC:	Namhyung Kim <namhyung@...nel.org>,
	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Pádraig Brady <P@...igBrady.com>,
	Michael Ellerman <mpe@...erman.id.au>,
	Dave Jones <davej@...emonkey.org.uk>,
	Luis Henriques <luis.henriques@...onical.com>,
	Shuah Khan <shuahkh@....samsung.com>
Subject: Re: [PATCH v2.1] ftracetest: Do not use usleep directly

On 04/02/2015 10:48 AM, Steven Rostedt wrote:
> On Thu, 02 Apr 2015 10:30:05 -0600
> Shuah Khan <shuahkh@....samsung.com> wrote:
> 
>>>> Anyway, I have this patch tagged for 4.1-rc2
>>>
>>> Why rc2?
>>
>> I usually let the patches stay in next for a few days before
>> I send pull request. It is getting close to that, so decided
>> on rc2 as a better choice.
>>
>> We are at rc-6 at the moment, maybe there is enough time for
>> this to get into rc-1
>>
> 
> But the merge window closes at the rc1 release. Is this also a "stable"
> thing? It should be labeled as such if that's the case.
> 

I am treating this as a fix so rc2 would be fine, however, if I can
get the rebased patch soon I can take it in for rc1.

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/