linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Daniel Bristot de Oliveira <bristot@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-trace-devel@vger.kernel.org,
	kernel test robot <lkp@intel.com>,
	Masami Hiramatsu <mhiramat@kernel.org>
Subject: Re: [PATCH 1/2] rv/dot2c: Make automaton definition static
Date: Thu, 20 Oct 2022 16:55:26 -0400	[thread overview]
Message-ID: <20221020165526.18dcaa02@gandalf.local.home> (raw)
In-Reply-To: <73cbfbaf-9397-00ab-4844-e5dd96958912@kernel.org>

On Wed, 19 Oct 2022 15:15:54 +0200
Daniel Bristot de Oliveira <bristot@kernel.org> wrote:

> On 10/19/22 00:25, Steven Rostedt wrote:
> > On Tue, 23 Aug 2022 17:20:28 +0200
> > Daniel Bristot de Oliveira <bristot@kernel.org> wrote:
> >   
> >> Monitor's automata definition is only used locally, so make dot2c generate
> >> a static definition.
> >>
> >> Link: https://lore.kernel.org/all/202208210332.gtHXje45-lkp@intel.com
> >> Link: https://lore.kernel.org/all/202208210358.6HH3OrVs-lkp@intel.com
> >>  
> > Somehow this fell through the cracks.
> > 
> > Daniel, is there any reason I shouldn't pull this in now?  
> 
> Oops... yes, it can be pulled.
> 

OK, I'm going to push this up as tools/urgent and send a pull request to
Linus.

-- Steve

      reply	other threads:[~2022-10-20 20:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-23 15:20 [PATCH 1/2] rv/dot2c: Make automaton definition static Daniel Bristot de Oliveira
2022-08-23 15:20 ` [PATCH 2/2] rv/monitors: Make monitor's automata " Daniel Bristot de Oliveira
2022-10-18 22:25 ` [PATCH 1/2] rv/dot2c: Make automaton " Steven Rostedt
2022-10-18 22:28   ` Steven Rostedt
2022-10-19 13:15   ` Daniel Bristot de Oliveira
2022-10-20 20:55     ` Steven Rostedt [this message]

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=20221020165526.18dcaa02@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=bristot@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mhiramat@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).