[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210902105158.3816e193@oasis.local.home>
Date: Thu, 2 Sep 2021 10:54:13 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Jiri Olsa <jolsa@...hat.com>
Cc: Alexei Starovoitov <alexei.starovoitov@...il.com>,
bpf <bpf@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Andrii Nakryiko <andriin@...com>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH 0/8] x86/ftrace: Add direct batch interface
On Wed, 1 Sep 2021 21:06:45 +0200 Jiri Olsa <jolsa@...hat.com> wrote:
> On Wed, Sep 01, 2021 at 08:23:38AM -0700, Alexei Starovoitov wrote:
> > Steven,
> >
> > Could you review and merge this set for this merge window,
> > so we can process related bpf bits for the next cycle?
>
> actually I might have sent it out too early, there's still
> bpf part review discussion that might end up in interface
> change
Regardless, it is way too late to apply this to the current merge
window. I don't think Linus would appreciate me pulling in a complex
patch set 4 days into the merge window, review it, and then push it to
him without much faith that this wont cause any major issues in use
cases we did not think about. Not to mention, I would have to drop
everything I am responsible for to do that.
I would never ask another maintainer to do such an irresponsible act.
>
> review would be great, but please hold on with the merge
I just got back from an 8 day vacation, and my inbox is way out of
hand, and I still need to put together the changes that have been in
linux-next for some time, and get that to Linus.
Hopefully I'll get to looking at this sometime next week.
-- Steve
Powered by blists - more mailing lists