From: Ingo Molnar <mingo@elte.hu>
To: "Frédéric Weisbecker" <fweisbec@gmail.com>
Cc: Pekka Paalanen <pq@iki.fi>,
rostedt@goodmis.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -tip 2/3] Tracing/ftrace: Adapt mmiotrace to the new type of print_line
Date: Mon, 29 Sep 2008 11:47:08 +0200 [thread overview]
Message-ID: <20080929094708.GA19252@elte.hu> (raw)
In-Reply-To: <c62985530809290228w2aae150dk97749159bd495c3b@mail.gmail.com>
* Frédéric Weisbecker <fweisbec@gmail.com> wrote:
> 2008/9/29 Ingo Molnar <mingo@elte.hu>:
> >
> > * Pekka Paalanen <pq@iki.fi> wrote:
> >
> >> > + return TRACE_TYPE_HANDLED;
> >> > }
> >> > }
> >>
> >> Otherwise, very good.
> >>
> >> As Ingo reverted the two earlier patches, you need to rebase these
> >> two. I'd like to see these in upstream. Let's handle the pipe closing
> >> bug in a different patch.
> >
> > good. Frederic, please just resubmit all fixes you have against
> > tip/master, with Pekka's Acked-by added. You can submit Pekka's patch as
> > well, so that it's a coherent series. The customary way for that is to
> > add in a From line as the first line of the changelog:
> >
> > From: Pekka Paalanen <pq@iki.fi>
> >
> > and add your signoff to the end of the changelog. This way Git will show
> > Pekka as the author and the path of the patch is well understood.
> >
>
> Ok so... I resend my patches (without changes?) but I adapt them to
> latest -tip master?
yeah - resend any bits not yet in tip/master, and also add Pekka's
Acked-by line to them where he said they are OK.
> And I add the pekka's patches (whit appropriate "from" line) with
> them?
Correct. Also mark it v2 perhaps in the announcement.
when there's NACKs and discussion it's (much) easier to pick up a new
series than picking out the bits from the discussion. That way the
resubmission might be redundant in a large part, but it's a summary of
your discussion with Pekka and the result of a consensus. I.e. not
redundant in terms of a workflow step.
Ingo
prev parent reply other threads:[~2008-09-29 9:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-26 15:44 [PATCH -tip 2/3] Tracing/ftrace: Adapt mmiotrace to the new type of print_line Frederic Weisbecker
2008-09-26 21:21 ` Pekka Paalanen
2008-09-27 12:17 ` Frédéric Weisbecker
2008-09-27 16:19 ` Ingo Molnar
2008-09-28 17:12 ` trace_pipe tentative fix (Re: [PATCH -tip 2/3] Tracing/ftrace: Adapt mmiotrace to the new type of print_line) Pekka Paalanen
2008-09-28 18:58 ` trace_pipe tentative fix Pekka Paalanen
2008-09-29 17:49 ` Frédéric Weisbecker
2008-09-29 9:20 ` trace_pipe tentative fix (Re: [PATCH -tip 2/3] Tracing/ftrace: Adapt mmiotrace to the new type of print_line) Frédéric Weisbecker
2008-09-28 16:29 ` [PATCH -tip 2/3] Tracing/ftrace: Adapt mmiotrace to the new type of print_line Pekka Paalanen
2008-09-29 9:02 ` Ingo Molnar
2008-09-29 9:28 ` Frédéric Weisbecker
2008-09-29 9:47 ` Ingo Molnar [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=20080929094708.GA19252@elte.hu \
--to=mingo@elte.hu \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pq@iki.fi \
--cc=rostedt@goodmis.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 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.