linux-kernel - Re: [PATCH -tip 2/3] Tracing/ftrace: Adapt mmiotrace to the new type of print

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <c62985530809290228w2aae150dk97749159bd495c3b@mail.gmail.com>
Date:	Mon, 29 Sep 2008 11:28:33 +0200
From:	"Frédéric Weisbecker" <fweisbec@...il.com>
To:	"Ingo Molnar" <mingo@...e.hu>
Cc:	"Pekka Paalanen" <pq@....fi>, rostedt@...dmis.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH -tip 2/3] Tracing/ftrace: Adapt mmiotrace to the new type of print_line

2008/9/29 Ingo Molnar <mingo@...e.hu>:
>
> * Pekka Paalanen <pq@....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@....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?
And I add the pekka's patches (whit appropriate "from" line) with them?

Sorry I 'm a bit lost....
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/