From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
mhiramat@kernel.org
Subject: Re: [GIT PULL] tracing: Updates for 4.20 (or 5.0)
Date: Wed, 31 Oct 2018 05:36:36 -0400 [thread overview]
Message-ID: <20181031053636.1063ed15@vmware.local.home> (raw)
In-Reply-To: <CAHk-=whmLFu=Cn2dti8oAAcPeVUSMeT_=uvuRvzdt-_xqjKSgQ@mail.gmail.com>
On Tue, 30 Oct 2018 10:02:16 -0700
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> As an explanation, the above kind of sucks. "SDT"? I had to look it
> up. I added a note to the commit message, but please, don't use random
> acronyms in kernel explanations unless they are industry-standard and
> comprehensible to kernel people.
>
> Good acronyms: "TLB", "WTF", "LOL". People know what those mean.
> "SDT"? Not so much.
Apologies, this is one of the reasons I wanted to wait till the end of
the week to do the pull request. I'm currently traveling (on my way
home), and using my laptop for all my work (at home I use my
workstation). I almost sent the pull request without even mentioning
the SDT work. That's because I had tested that and pushed it into
linux-next some time ago and completely forgot about it. I caught the
error looking at the patches before sending, redid the signed tag by
mentioning it and sent it out.
I would have had a deeper explanation about the change otherwise. I
really hate merge windows while I'm traveling :-(
-- Steve
prev parent reply other threads:[~2018-10-31 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 13:37 Steven Rostedt
2018-10-30 17:02 ` Linus Torvalds
2018-10-31 9:36 ` 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=20181031053636.1063ed15@vmware.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®