From: Thomas Gleixner <tglx@linutronix.de>
To: GeunSik Lim <leemgs1@gmail.com>
Cc: Steven Rostedt <srostedt@redhat.com>, Ingo Molnar <mingo@elte.hu>,
rt-users <linux-rt-users@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Update old Mini-HOWTO for ftrace
Date: Tue, 7 Apr 2009 01:32:12 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.0904070120090.21577@localhost.localdomain> (raw)
In-Reply-To: <49b7c2350904061609q7984d5f0u478a092ffcabe12c@mail.gmail.com>
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
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-06 23:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 14:02 GeunSik Lim
2009-04-06 14:17 ` GeunSik Lim
2009-04-06 23:09 ` GeunSik Lim
2009-04-06 23:32 ` Thomas Gleixner [this message]
2009-04-07 0:37 ` Steven Rostedt
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=alpine.LFD.2.00.0904070120090.21577@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=leemgs1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=srostedt@redhat.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®