From: Tao Ma <tao.ma@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 4/5] ocfs2: Add ocfs2_trace.h.
Date: Wed, 10 Nov 2010 22:33:37 +0800 [thread overview]
Message-ID: <4CDAAD41.8080900@oracle.com> (raw)
In-Reply-To: <20101110094803.GE31158@mail.oracle.com>
Joel Becker wrote:
> On Wed, Nov 10, 2010 at 10:52:22AM +0800, Tao Ma wrote:
>
>> About one year ago, Wengang Wang tried some first steps
>> to add tracepoints to ocfs2. But at that time we don't
>> have ocfs2 1.6 introduced, so we delay this work until now
>> after ocfs2 1.6 and UEK(Unbreakable Enterprise Kernel) are
>> released.
>>
>> Wengang's original patch is here:
>> http://oss.oracle.com/pipermail/ocfs2-devel/2009-November/005512.html
>>
>> But as Steven Rostedt indicated in his article
>> http://lwn.net/Articles/383362/, we'd better have our trace
>> files resides in fs/ocfs2, so I rewrited the patch using the
>> method Steven mentioned in that article.
>>
>> Signed-off-by: Wengang Wang <wen.gang.wang@oracle.com>
>> Signed-off-by: Tao Ma <tao.ma@oracle.com>
>>
>
> Did you author this or did Wengang? If you are the author, only
> your signoff is necessary. You should, of course, credit him in the
> description, and you can get his Acked-by: if you feel it necessary.
>
Yeah, sorry, I forgot to add a "From:Wengang Wang
<wen.gang.wang@oracle.com>" in my guilt.
That way, it will generate the commit with Author of wengang wang
automatically. Since this patch only
includes about 19 lines of change, and I changed about 5-6 lines, the
author should be him.
> I realize this patch is only a slight difference from his
> original, so he could perhaps still be considered the author. I'm
> unsure how much rewriting you did in the second patch, though.
>
As for the 2nd one, his original patch has this diffstat:
fs/ocfs2/alloc.c | 47 +++++-----
include/trace/events/ocfs2.h | 202
++++++++++++++++++++++++++++++++++++++++++
2 files changed, 224 insertions(+), 25 deletions(-)
My patch has
fs/ocfs2/alloc.c | 165 +++++++++--------
fs/ocfs2/ocfs2_trace.h | 485 ++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 573 insertions(+), 77 deletions(-)
So I guess the author should be me(What's more, I have changed some of
his modifications also.)?
Or I should leave his patch there with his sob, while adding a new patch
of mine?
Regards,
Tao
next prev parent reply other threads:[~2010-11-10 14:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 2:51 [Ocfs2-devel] [PATCH 0/5] The first try of adding trace event to ocfs2 Tao Ma
2010-11-10 2:52 ` [Ocfs2-devel] [PATCH 1/5] ocfs2: Remove unused truncate function from alloc.c Tao Ma
2010-11-10 9:41 ` Joel Becker
2010-11-10 2:52 ` [Ocfs2-devel] [PATCH 2/5] ocfs2: Remove ENTRY from masklog Tao Ma
2010-11-10 9:43 ` Joel Becker
2010-11-10 14:19 ` Tao Ma
2010-11-10 2:52 ` [Ocfs2-devel] [PATCH 3/5] ocfs2: Remove EXIT " Tao Ma
2010-11-10 9:45 ` Joel Becker
2010-11-10 14:22 ` Tao Ma
2010-11-10 2:52 ` [Ocfs2-devel] [PATCH 4/5] ocfs2: Add ocfs2_trace.h Tao Ma
2010-11-10 9:48 ` Joel Becker
2010-11-10 14:33 ` Tao Ma [this message]
2010-11-10 22:19 ` Joel Becker
2010-11-10 2:52 ` [Ocfs2-devel] [PATCH 5/5] ocfs2: Remove mlog(0) from fs/ocfs2/alloc.c Tao Ma
2010-11-10 9:50 ` Joel Becker
2010-11-10 14:39 ` Tao Ma
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=4CDAAD41.8080900@oracle.com \
--to=tao.ma@oracle.com \
--cc=ocfs2-devel@oss.oracle.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;
as well as URLs for NNTP newsgroup(s).