From: Shuah Khan <shuahkh@osg.samsung.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "Namhyung Kim" <namhyung@kernel.org>,
"Masami Hiramatsu" <masami.hiramatsu.pt@hitachi.com>,
LKML <linux-kernel@vger.kernel.org>,
"Pádraig Brady" <P@draigBrady.com>,
"Michael Ellerman" <mpe@ellerman.id.au>,
"Dave Jones" <davej@codemonkey.org.uk>,
"Luis Henriques" <luis.henriques@canonical.com>,
"Shuah Khan" <shuahkh@osg.samsung.com>
Subject: Re: [PATCH v2.1] ftracetest: Do not use usleep directly
Date: Thu, 02 Apr 2015 10:52:38 -0600 [thread overview]
Message-ID: <551D73D6.6030100@osg.samsung.com> (raw)
In-Reply-To: <20150402124829.5b617bcd@gandalf.local.home>
On 04/02/2015 10:48 AM, Steven Rostedt wrote:
> On Thu, 02 Apr 2015 10:30:05 -0600
> Shuah Khan <shuahkh@osg.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@osg.samsung.com | (970) 217-8978
next prev parent reply other threads:[~2015-04-02 16:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 4:24 [PATCH v2] ftracetest: Do not use usleep directly Namhyung Kim
2015-04-02 4:34 ` [PATCH v2.1] " Namhyung Kim
2015-04-02 5:58 ` Masami Hiramatsu
2015-04-02 13:38 ` Steven Rostedt
2015-04-02 14:20 ` Shuah Khan
2015-04-02 15:08 ` Steven Rostedt
2015-04-02 16:30 ` Shuah Khan
2015-04-02 16:48 ` Steven Rostedt
2015-04-02 16:52 ` Shuah Khan [this message]
2015-04-02 17:26 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=551D73D6.6030100@osg.samsung.com \
--to=shuahkh@osg.samsung.com \
--cc=P@draigBrady.com \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=luis.henriques@canonical.com \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mpe@ellerman.id.au \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox