public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Johannes Weiner <hannes@saeurebad.de>
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:25 +0200	[thread overview]
Message-ID: <87pro5ywgu.fsf@basil.nowhere.org> (raw)
In-Reply-To: <87skt16u4a.fsf@skyscraper.fehenstaub.lan> (Johannes Weiner's message of "Tue, 19 Aug 2008 14:56:37 +0200")

Johannes Weiner <hannes@saeurebad.de> writes:
>
> You probably misconfigured emacs then.  I ran checkpatch over your patch
> and don't see how and why emacs would add trailing whitespace after a
> opening brace.

I don't know how, but it does. vim does too sometimes (I use both
editors) 

>
> You can use this to be on the safe side:
>
> (add-hook 'before-save-hook 'delete-trailing-whitespace)

That drops it on all. This means when I edit something which already
has trailing spaces then the diff is full of noise. That would
be a cure far worse than the disease[1]

Ideal would be if git-commit dropped them on all new lines, similar to 
git-apply --whitespace=fix and quilt refresh, but it doesn't seem to know how.

But normally maintainers just set these options (at least I do and Andrew
does too) so it doesn't really matter if the submitted patch has trailing 
spaces or not because they disappear on the way up. 

And that said I refuse to write any more on this silly bike shed topic.

-Andi

[1] to be honest I'm not sure i are actually a disease since I don't
know of any single problem they cause.

  reply	other threads:[~2008-08-19 13:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-18 20:32 oprofile + hibernation = badness 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 [this message]
2008-08-19 13:18         ` Ingo Molnar
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=87pro5ywgu.fsf@basil.nowhere.org \
    --to=andi@firstfloor.org \
    --cc=hannes@saeurebad.de \
    --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