From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Beau Belgrave <beaub@linux.microsoft.com>,
Chengming Zhou <zhouchengming@bytedance.com>,
Huang Yiwei <quic_hyiwei@quicinc.com>,
John Garry <john.g.garry@oracle.com>,
Randy Dunlap <rdunlap@infradead.org>,
Thorsten Blum <thorsten.blum@toblux.com>,
Vincent Donnefort <vdonnefort@google.com>,
linke li <lilinke99@qq.com>,
Daniel Bristot de Oliveira <bristot@redhat.com>
Subject: Re: [GIT PULL] tracing: Updates for v6.9
Date: Sun, 17 Mar 2024 08:14:44 -0400 [thread overview]
Message-ID: <20240317081444.189fa238@rorschach.local.home> (raw)
In-Reply-To: <CAHk-=wgKJti5WBi7VmA_ETDiXjmkEqvVW7De5ajwtkyJ=c==kA@mail.gmail.com>
On Sat, 16 Mar 2024 11:42:42 -0700
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Sat, 16 Mar 2024 at 11:20, Steven Rostedt <rostedt@goodmis.org> wrote:
> >
> > 1) Rebase without them (I know how much you love rebasing)
>
> This.
>
> Except honestly, the pulls are getting to be so complicated for me
> because I have to check them, that I'd really like you to start doing
> topic branches for individual things.
>
We started doing that (with the trace probes and tools). But sure, I
can make a few more topic branches.
>
> Do you have to do it for the current situation where I just can't take
> the mmap stuff? No. But please look at it going forward.
Since I had to do a rebase, I'm rebasing it off of the last pull you
did from me for some fixes that didn't make it into 6.8. That way it
will include the fix in your tree that I need to add the string checks
for the TRACE_EVENT() __assign_str() and __string() checks.
I'm testing everything now.
-- Steve
prev parent reply other threads:[~2024-03-17 12:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 16:29 Steven Rostedt
2024-03-16 16:31 ` Linus Torvalds
2024-03-16 16:59 ` Linus Torvalds
2024-03-16 18:18 ` Linus Torvalds
2024-03-16 18:20 ` Steven Rostedt
2024-03-16 18:42 ` Linus Torvalds
2024-03-16 20:00 ` Borislav Petkov
2024-03-16 20:42 ` Linus Torvalds
2024-03-16 21:07 ` Borislav Petkov
2024-03-17 12:14 ` 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=20240317081444.189fa238@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=beaub@linux.microsoft.com \
--cc=bristot@redhat.com \
--cc=john.g.garry@oracle.com \
--cc=lilinke99@qq.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=quic_hyiwei@quicinc.com \
--cc=rdunlap@infradead.org \
--cc=thorsten.blum@toblux.com \
--cc=torvalds@linux-foundation.org \
--cc=vdonnefort@google.com \
--cc=zhouchengming@bytedance.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
all inboxes | Powered by JetHome®