From: Steven Rostedt <rostedt@goodmis.org>
To: Viktor Rosendahl <viktor.rosendahl@gmail.com>
Cc: Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org,
Joel Fernandes <joel@joelfernandes.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v5 2/4] preemptirq_delay_test: Add the burst feature and a sysfs trigger
Date: Thu, 5 Sep 2019 12:52:27 -0400 [thread overview]
Message-ID: <20190905125227.2638e406@oasis.local.home> (raw)
In-Reply-To: <4e1c66b8-4aee-77d3-cf3b-dc633f9abf6b@gmail.com>
On Wed, 4 Sep 2019 21:10:38 +0200
Viktor Rosendahl <viktor.rosendahl@gmail.com> wrote:
> On 9/4/19 1:42 PM, Steven Rostedt wrote:
> > On Tue, 3 Sep 2019 15:26:00 +0200
> > Viktor Rosendahl <viktor.rosendahl@gmail.com> wrote:
> >> diff --git a/kernel/trace/preemptirq_delay_test.c b/kernel/trace/preemptirq_delay_test.c
> >> index d8765c952fab..dc281fa75198 100644
> >> --- a/kernel/trace/preemptirq_delay_test.c
> >> +++ b/kernel/trace/preemptirq_delay_test.c
> >> @@ -3,6 +3,7 @@
> >> * Preempt / IRQ disable delay thread to test latency tracers
> >> *
> >> * Copyright (C) 2018 Joel Fernandes (Google) <joel@joelfernandes.org>
> >> + * Copyright (C) 2018, 2019 BMW Car IT GmbH
> >
> > A name and what you did should also be attached here. Ideally, we leave
> > these out as git history is usually enough.
>
> I am not so keen to clutter source files with a new copyright message.
> My problem is that git-send-email doesn't work well with my work email
> address, so I am forced to use my private gmail, which may create a
> false impression that I as a private individual would be the copyright
> holder.
>
Then do what I do:
Steven Rostedt (VMware) <rostedt@goodmis.org>
I did "(Red Hat)" when I worked for Red Hat.
-- Steve
next prev parent reply other threads:[~2019-09-05 16:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 13:25 [PATCH v5 0/4] Some new features for the preempt/irqsoff tracers Viktor Rosendahl
2019-09-03 13:25 ` [PATCH v5 1/4] ftrace: Implement fs notification for tracing_max_latency Viktor Rosendahl
2019-09-04 4:00 ` Joel Fernandes
2019-09-04 8:19 ` Peter Zijlstra
2019-09-04 13:42 ` Joel Fernandes
2019-09-04 18:17 ` Viktor Rosendahl
2019-09-04 10:21 ` Paul E. McKenney
2019-09-04 8:20 ` Peter Zijlstra
2019-09-04 11:37 ` Steven Rostedt
2019-09-04 11:39 ` Steven Rostedt
2019-09-04 19:00 ` Viktor Rosendahl
2019-09-03 13:26 ` [PATCH v5 2/4] preemptirq_delay_test: Add the burst feature and a sysfs trigger Viktor Rosendahl
2019-09-04 11:42 ` Steven Rostedt
2019-09-04 19:10 ` Viktor Rosendahl
2019-09-05 16:52 ` Steven Rostedt [this message]
2019-09-05 18:27 ` Viktor Rosendahl
2019-09-03 13:26 ` [PATCH v5 3/4] Add the latency-collector to tools Viktor Rosendahl
2019-09-03 13:26 ` [PATCH v5 4/4] ftrace: Add an option for tracing console latencies Viktor Rosendahl
2019-09-04 5:02 ` kbuild test robot
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=20190905125227.2638e406@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=viktor.rosendahl@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.