From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Corey Minyard <cminyard@mvista.com>,
minyard@acm.org, rostedt@goodmis.org
Cc: linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org,
tglx@linutronix.d, C.Emde@osadl.org, jkacur@redhat.com,
paul.gortmaker@windriver.com
Subject: Re: [PATCH] tracing: Always run per-cpu ring buffer resize with schedule_work_on()
Date: Tue, 29 Jul 2014 10:59:41 +0200 [thread overview]
Message-ID: <53D7627D.10005@linutronix.de> (raw)
In-Reply-To: <53D6C601.7090803@mvista.com>
On 07/28/2014 11:52 PM, Corey Minyard wrote:
> Ping, I haven't heard anything on this.
I looks good from my point of view.
Sebastian
next prev parent reply other threads:[~2014-07-29 8:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 19:07 [PATCH] tracing: Always run per-cpu ring buffer resize with schedule_work_on() minyard
2014-07-28 21:52 ` Corey Minyard
2014-07-29 8:59 ` Sebastian Andrzej Siewior [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-28 21:32 minyard
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=53D7627D.10005@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=C.Emde@osadl.org \
--cc=cminyard@mvista.com \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=minyard@acm.org \
--cc=paul.gortmaker@windriver.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.d \
/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;
as well as URLs for NNTP newsgroup(s).