public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: John Kacur <jkacur@redhat.com>
To: Frank Rowand <frank.rowand@am.sony.com>
Cc: "jkacur@redhat.com" <jkacur@redhat.com>,
	"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
	Clark Williams <williams@redhat.com>,
	Bhavesh Davda <bhavesh@vmware.com>
Subject: Re: [PATCH] cyclictest: white space cleanup
Date: Wed, 30 Jan 2013 18:00:49 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.03.1301301756450.4078@tycho> (raw)
In-Reply-To: <5107303E.3010208@am.sony.com>



On Mon, 28 Jan 2013, Frank Rowand wrote:

> On 01/28/13 18:09, Frank Rowand wrote:
> > Clean up cyclictest formatting:
> >   Change leading spaces to tabs.
> >   Align function parameters.
> >   Place type of function on same line as function name.
> > 
> > Signed-off-by: Frank Rowand <frank.rowand@am.sony.com>
> > ---
> >  src/cyclictest/cyclictest.c |   43 	21 +	22 -	0 !
> >  1 file changed, 21 insertions(+), 22 deletions(-)
> > 
> 
> < snip >
> 
> The motivation of the white space clean up is so that future
> patches will not add white space damage.  Many editors will
> automatically copy the bad white space if a line immediately
> following is added.
> 
> I tried to not get carried away with other formatting clean
> up.  The alignment of function parameters was only a few
> locations and seemed in the spirit of white space clean up.
> 
> The "type of function name" fix was getting carried away, but
> there was only one instance so I don't feel too guilty.
> 

Okay, this is fine. Whitespace patches can be annoying though when they 
cause conflicts, I had to apply this before patches from Bhavesh Davda
but I understand your motivation.

Applied and in my devel repo to be pushed to Clark

Thanks

      reply	other threads:[~2013-01-30 17:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29  2:09 [PATCH] cyclictest: white space cleanup Frank Rowand
2013-01-29  2:13 ` Frank Rowand
2013-01-30 17:00   ` John Kacur [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=alpine.LFD.2.03.1301301756450.4078@tycho \
    --to=jkacur@redhat.com \
    --cc=bhavesh@vmware.com \
    --cc=frank.rowand@am.sony.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=williams@redhat.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