From: Steven Rostedt <rostedt@goodmis.org>
To: Tom Zanussi <tom.zanussi@linux.intel.com>
Cc: Jean-Jacques Hiblot <jjhiblot@traphandler.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Tracing events with GPIOs
Date: Tue, 17 Dec 2013 14:05:02 -0500 [thread overview]
Message-ID: <20131217140502.2aed31aa@gandalf.local.home> (raw)
In-Reply-To: <1387304970.3051.35.camel@empanada>
On Tue, 17 Dec 2013 12:29:30 -0600
Tom Zanussi <tom.zanussi@linux.intel.com> wrote:
> > Tom,
> > is git://git.yoctoproject.org/linux-yocto-contrib
> > tzanussi/event-triggers-v11 the right starting point ?
> >
>
> Yep, that's the last iteration - I haven't changed anything since then.
>
Is this the same as the last patch series you sent out? I started
testing them again last week, but they failed some of my tests.
Unfortunately, I didn't get a chance to look into why. I'm hoping to
get that series out to my for-next branch by end of the week, as I'll
be taking two weeks off starting next week.
Year end crap is piling up, preventing me from getting real work
done ;-)
-- Steve
next prev parent reply other threads:[~2013-12-17 19:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 0:22 [PATCH] Tracing events with GPIOs Jean-Jacques Hiblot
2013-12-17 1:16 ` Masami Hiramatsu
2013-12-17 17:22 ` Jean-Jacques Hiblot
2013-12-17 18:29 ` Tom Zanussi
2013-12-17 19:05 ` Steven Rostedt [this message]
2013-12-17 20:45 ` Tom Zanussi
2013-12-31 10:16 ` Jean-Jacques Hiblot
2013-12-19 6:52 ` Alexandre Courbot
2013-12-19 11:38 ` Jean-Jacques Hiblot
2013-12-20 7:33 ` Alexandre Courbot
2013-12-20 8:40 ` Jean-Jacques Hiblot
2014-01-03 10:50 ` Alexandre Courbot
2014-01-03 16:39 ` Jean-Jacques Hiblot
2014-01-02 12:43 ` Linus Walleij
2014-01-03 16:32 ` Jean-Jacques Hiblot
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=20131217140502.2aed31aa@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=jjhiblot@traphandler.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=tom.zanussi@linux.intel.com \
/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).