From: Steven Rostedt <rostedt@goodmis.org>
To: "Robin H. Johnson" <robbat2@gentoo.org>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com,
rjohnson@digitalocean.com, Peter Zijlstra <peterz@infradead.org>,
Jiri Olsa <jolsa@redhat.com>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH 1/2] tracing: show size of requested buffer
Date: Wed, 6 Oct 2021 20:55:40 -0400 [thread overview]
Message-ID: <20211006205540.14ea13e0@rorschach.local.home> (raw)
In-Reply-To: <robbat2-20211006T224617-864445788Z@orbis-terrarum.net>
On Wed, 6 Oct 2021 22:48:35 +0000
"Robin H. Johnson" <robbat2@gentoo.org> wrote:
> On Wed, Oct 06, 2021 at 06:26:52PM -0400, Steven Rostedt wrote:
> > On Mon, 30 Aug 2021 21:37:22 -0700
> > "Robin H. Johnson" <robbat2@gentoo.org> wrote:
> >
> > Sorry for the late reply, I was on holiday when this was sent, and I'm just
> > getting to looking at this email now (as my OoO email should have suggested ;-)
> >
> > Anyway, this needs to be reviewed by the Perf maintainers (Cc'd)
> >
> > (Lore link for patch 2:
> > https://lore.kernel.org/all/20210831043723.13481-2-robbat2@gentoo.org/ )
>
> You already CC'd them on Sept 7th, no response yet.
Oh good, that means I'm not the one that dropped the ball on this ;-)
>
> Does MAINTAINERS need an update for kernel/trace/trace_event_perf.c?
> It points to Ingo & yourself for that directory, and not to the Perf
> maintainers.
Well, it is maintained by both of us. I usually just ask them to review
before taking it, but if there's no response from them by the end of
the week, I'll add it to my "for-next" queue.
-- Steve
prev parent reply other threads:[~2021-10-07 0:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 4:37 [PATCH 1/2] tracing: show size of requested buffer Robin H. Johnson
2021-08-31 4:37 ` [PATCH 2/2] tracing: increase PERF_MAX_TRACE_SIZE to handle Sentinel1 and docker together Robin H. Johnson
2021-09-08 1:24 ` [PATCH 1/2] tracing: show size of requested buffer Steven Rostedt
2021-10-07 7:11 ` Peter Zijlstra
2021-10-07 13:23 ` Steven Rostedt
2021-10-07 17:26 ` Robin H. Johnson
2021-10-08 22:13 ` Steven Rostedt
2021-10-09 0:21 ` Robin H. Johnson
2021-10-26 20:43 ` Steven Rostedt
2021-10-26 21:23 ` Peter Zijlstra
2021-10-26 21:26 ` Steven Rostedt
2021-10-06 22:26 ` Steven Rostedt
2021-10-06 22:48 ` Robin H. Johnson
2021-10-07 0: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=20211006205540.14ea13e0@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rjohnson@digitalocean.com \
--cc=robbat2@gentoo.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