From: Ingo Molnar <mingo@elte.hu>
To: Andi Kleen <ak@linux.intel.com>
Cc: Vegard Nossum <vegard.nossum@gmail.com>,
Pavel Machek <pavel@suse.cz>, "Rafael J. Wysocki" <rjw@sisk.pl>,
Robert Richter <robert.richter@amd.com>,
Philippe Elie <phil.el@wanadoo.fr>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: oprofile + hibernation = badness
Date: Tue, 19 Aug 2008 15:18:47 +0200 [thread overview]
Message-ID: <20080819131847.GA31605@elte.hu> (raw)
In-Reply-To: <48AAB8B6.3020802@linux.intel.com>
* Andi Kleen <ak@linux.intel.com> wrote:
>> Andi, another issue: your patch had 5 spurious whitespace errors.
>> This is a reoccuring, many years pattern of behavior from you and you
>> need to fix your workflow to send less sloppy patches.
>
> Yes I forgot you define patch cleanness based on white space.
>
> Seriously, It's actually new -- i did this one in git directly instead
> of quilt and git-commit doesn't seem to know how to drop them. In my
> older quilt workflow they were always automatically dropped since many
> years. Both emacs and vim add them and I don't plan to switch editors,
> sorry.
Thousands of other kernel developers get it right and manage to submit
clean patches, so i think you are not trying very hard to actually solve
this problem - and your flippant and obtrusive answers do not make it
very easy to work with you as a contributor.
>> I fixed up the problems of this patch, no need to resend.
>
> I hope you fixed the typos in the commit log too (it really was just a
> RFC test patch)
You've put your signoff in there and Vegard has tested it. The general
principle on lkml is that patches can be marked as do-not-apply-yet by
adding something like this:
Not-Signed-off-by: Andi Kleen <ak@linux.intel.com>
or by not adding a SOB line at all. In that case i either ask people for
the SOB or apply them at my own risk.
Thanks,
Ingo
next prev parent reply other threads:[~2008-08-19 13:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-18 20:32 Vegard Nossum
2008-08-18 20:51 ` Rafael J. Wysocki
2008-08-18 21:08 ` Vegard Nossum
2008-08-18 21:15 ` Rafael J. Wysocki
2008-08-18 21:29 ` Andrew Morton
2008-08-19 1:13 ` Andi Kleen
2008-08-19 7:12 ` Vegard Nossum
2008-08-19 9:49 ` Ingo Molnar
2008-08-19 12:12 ` Andi Kleen
2008-08-19 12:37 ` Robert Richter
2008-08-19 12:56 ` Johannes Weiner
2008-08-19 13:18 ` Andi Kleen
2008-08-19 13:18 ` Ingo Molnar [this message]
2008-09-01 16:34 ` Robert Richter
2008-09-05 17:58 ` Ingo Molnar
2008-09-05 18:59 ` Robert Richter
2008-09-05 20:31 ` Ingo Molnar
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=20080819131847.GA31605@elte.hu \
--to=mingo@elte.hu \
--cc=ak@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=phil.el@wanadoo.fr \
--cc=rjw@sisk.pl \
--cc=robert.richter@amd.com \
--cc=vegard.nossum@gmail.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
Powered by JetHome