linux-kernel - Re: [Patch 1/3] Tracing/ftrace: Make nop tracer reset previous entries

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: <c62985530809220506o39264e63k25ccb7a73384335c@mail.gmail.com>
Date:	Mon, 22 Sep 2008 14:06:44 +0200
From:	"Frédéric Weisbecker" <fweisbec@...il.com>
To:	"Ingo Molnar" <mingo@...e.hu>
Cc:	"KOSAKI Motohiro" <kosaki.motohiro@...fujitsu.com>,
	"Linux Kernel" <linux-kernel@...r.kernel.org>,
	"Steven Rostedt" <rostedt@...dmis.org>,
	"Steven Noonan" <steven@...inklabs.net>
Subject: Re: [Patch 1/3] Tracing/ftrace: Make nop tracer reset previous entries

2008/9/22 Ingo Molnar <mingo@...e.hu>:
>
> * KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com> wrote:
>
>> your patch seems corrupted.
>> please check again your e-mail client settings.
>
> i fixed the extra newlines up and applied the patches to
> tip/tracing/ftrace, thanks Frédéric!
>
> please check Documentation/email-clients.txt about details. There were
> two problems i saw: overlong lines in the commit description and extra
> 'double newlines' in the patch itself. (To get around gmail limitations
> you can send -tip patches as MIME attachments as well.)
>
>        Ingo
>

Oops. I'm really sorry about that. I was pretty convinced that my
email client was well configured.
In the future I will first send myself the patches before any new
submit to ensure they are not damaged...

Thanks.
--
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/