linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-trace-devel@vger.kernel.org,
	Ingo Molnar <mingo@kernel.org>, Jiri Olsa <jolsa@redhat.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/6] tools/lib/traceevent: Man page updates and some file movement
Date: Mon, 23 Sep 2019 11:12:48 -0400	[thread overview]
Message-ID: <20190923111248.5ebdbfd5@oasis.local.home> (raw)
In-Reply-To: <20190923145249.GF16544@kernel.org>

On Mon, 23 Sep 2019 11:52:49 -0300
Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com> wrote:

> Em Mon, Sep 23, 2019 at 11:39:27AM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Mon, Sep 23, 2019 at 11:28:39AM -0300, Arnaldo Carvalho de Melo escreveu:  
> > > Em Thu, Sep 19, 2019 at 05:23:35PM -0400, Steven Rostedt escreveu:  
> > > > Hi Arnaldo,
> > > > 
> > > > This is a series of man page updates to the libtraceevent code, as
> > > > well as a fix to one missing prototype and some movement of the location
> > > > of the plugins (to have the plugins in their own directory).  
> >    
> > > Thanks, applied.  
> > 
> > Its breaking the build on Ubuntu 19.04 cross building to aarch64, I'll
> > see if I can fix it:  
> 
> Makefiles really suck, so I'm removing this one till we get this sorted
> out:
> 
> "Move traceevent plugins in its own subdirectory"
> 
> Ok?

Yeah. Let's not apply this one yet till we figure out what broke. I'll
take a look at it too.

Thanks!

-- Steve

  reply	other threads:[~2019-09-23 15:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-19 21:23 [PATCH 0/6] tools/lib/traceevent: Man page updates and some file movement Steven Rostedt
2019-09-19 21:23 ` [PATCH 1/6] tools/lib/traceevent: Man pages for libtraceevent event print related API Steven Rostedt
2019-09-19 21:23 ` [PATCH 2/6] tools/lib/traceevent: Man pages fix, rename tep_ref_get() to tep_get_ref() Steven Rostedt
2019-09-19 21:23 ` [PATCH 3/6] tools/lib/traceevent: Man pages fix, changes in event printing APIs Steven Rostedt
2019-09-19 21:23 ` [PATCH 4/6] tools/lib/traceevent: Add tep_get_event() in event-parse.h Steven Rostedt
2019-09-19 21:23 ` [PATCH 5/6] tools/lib/traceevent: Man pages for tep plugins APIs Steven Rostedt
2019-09-19 21:23 ` [PATCH 6/6] tools/lib/traceevent: Move traceevent plugins in its own subdirectory Steven Rostedt
2019-09-23 14:28 ` [PATCH 0/6] tools/lib/traceevent: Man page updates and some file movement Arnaldo Carvalho de Melo
2019-09-23 14:39   ` Arnaldo Carvalho de Melo
2019-09-23 14:52     ` Arnaldo Carvalho de Melo
2019-09-23 15:12       ` Steven Rostedt [this message]
2019-09-23 15:59         ` Steven Rostedt
2019-09-23 17:38           ` Arnaldo Carvalho de Melo

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=20190923111248.5ebdbfd5@oasis.local.home \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=arnaldo.melo@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.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;
as well as URLs for NNTP newsgroup(s).