From: Ingo Molnar <mingo@elte.hu>
To: "Frédéric Weisbecker" <fweisbec@gmail.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Steven Noonan <steven@uplinklabs.net>
Subject: Re: [Patch 1/3] Tracing/ftrace: Make nop tracer reset previous entries
Date: Mon, 22 Sep 2008 14:10:10 +0200 [thread overview]
Message-ID: <20080922121010.GA20242@elte.hu> (raw)
In-Reply-To: <c62985530809220506o39264e63k25ccb7a73384335c@mail.gmail.com>
* Frédéric Weisbecker <fweisbec@gmail.com> wrote:
> 2008/9/22 Ingo Molnar <mingo@elte.hu>:
> >
> > * KOSAKI Motohiro <kosaki.motohiro@jp.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...
no harm was done really, we can cope. I'd suggest you do the
send-yourself thing once now to check that your practices are OK.
Ingo
prev parent reply other threads:[~2008-09-22 12:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-21 18:10 [Patch 1/3] Tracing/ftrace: Make nop tracer reset previous entries Frédéric Weisbecker
2008-09-22 3:13 ` KOSAKI Motohiro
2008-09-22 9:36 ` Ingo Molnar
2008-09-22 12:06 ` Frédéric Weisbecker
2008-09-22 12:10 ` 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=20080922121010.GA20242@elte.hu \
--to=mingo@elte.hu \
--cc=fweisbec@gmail.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=steven@uplinklabs.net \
/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