From: Steven Rostedt <srostedt@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: GeunSik Lim <leemgs1@gmail.com>, Ingo Molnar <mingo@elte.hu>,
rt-users <linux-rt-users@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] Update old Mini-HOWTO for ftrace
Date: Mon, 06 Apr 2009 20:37:14 -0400 [thread overview]
Message-ID: <1239064634.4753.10.camel@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.00.0904070120090.21577@localhost.localdomain>
On Tue, 2009-04-07 at 01:32 +0200, Thomas Gleixner wrote:
> GeunSik,
>
> On Tue, 7 Apr 2009, GeunSik Lim wrote:
>
> > Sorry,
> > I mistake because I don't understand how to submit patch exactly.
>
> To submit a patch you need to have:
>
> 1) useful subject line
>
> [PATCH] subsystem: what does the patch do
>
> subsystem in your care is: ftrace
>
> 2) useful patch description
>
> explains what the patch does. Which bug/problem it fixes or which
> enhancement it provides
>
> Look at the git log. Each commit has an (more or lesss) usefull
> description, but you get the idea. If you see a confusing or
> cryptic description you need way more time to figure out what the
> patch does or what it is supposed to do.
>
> 3) Your Signed-off-by
>
> Signed-off-by is the certificate of origin as described in
>
> Documentation/SubmittingPatches
>
> You can only add your own Signed-off-by. You never can add the
> Signed-off-by of some one else.
>
> > I just appended below "singned-off" contents for convenience.
> > Sorry again.
> >
> > Signed-off-by: GeunSik Lim <leemgs1@gmail.com>
> > Signed-off-by: Steven Rostedt <srostedt@redhat.com>
> > Signed-off-by: Ingo Molnar <mingo@elte.hu>
>
> That's how it might look later on. It would say:
>
> GeunSik Lim wrote the patch
> Steven Rostedt picked it up from your mail and sent it to Ingo
Please send to my rostedt@goodmis.org account. From now on I'm using
that as my Signed-off-by and keep Red Hat as the author. I'm about to
travel and I do not read my Red Hat email while I'm out.
I'll pick this patch up now before I leave.
Thanks,
-- Steve
> Ingo Molnar received it from Steven's mail and applied it
>
> There is no way for you to forsee how your patch will be picked up and
> propagated. It might go via Andrew Morton or directly to Linus. Ok ?
>
> So you only add your own Signed-off-by.
>
> Hope that helps. Thanks,
>
> tglx
next prev parent reply other threads:[~2009-04-07 0:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 14:02 [PATCH] Update old Mini-HOWTO for ftrace GeunSik Lim
2009-04-06 14:17 ` GeunSik Lim
2009-04-06 23:09 ` GeunSik Lim
2009-04-06 23:32 ` Thomas Gleixner
2009-04-07 0:37 ` Steven Rostedt [this message]
2009-04-07 1:25 ` Minchan Kim
2009-04-07 1:26 ` Steven Rostedt
2009-04-07 4:37 ` GeunSik Lim
2009-04-07 1:46 ` Steven Rostedt
2009-04-07 5:08 ` GeunSik Lim
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=1239064634.4753.10.camel@localhost.localdomain \
--to=srostedt@redhat.com \
--cc=leemgs1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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).