xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: tim@xen.org, xen-devel@lists.xensource.com,
	stefano.stabellini@citrix.com, david.vrabel@citrix.com
Subject: Re: [PATCH] arm: fixup hard tabs
Date: Mon, 13 Feb 2012 18:26:33 +0000	[thread overview]
Message-ID: <4F3955D9.2020900@citrix.com> (raw)
In-Reply-To: <63e88a26e1ef58c8e5a2.1329156229@cosworth.uk.xensource.com>

On 13/02/12 18:03, Ian Campbell wrote:
> # HG changeset patch
> # User Ian Campbell <ian.campbell@citrix.com>
> # Date 1329153968 0
> # Node ID 63e88a26e1ef58c8e5a2b30a003ab7c3bc9c6b54
> # Parent  7fd8f10cfd3eaf9f0982eb6fd49334a1e229ba98
> arm: fixup hard tabs
> 
> Unfortunately the tool I was using to apply patches mangles hard tabs. This
> patch corrects this in the effected files (which is fortunately only a subset
> of .S or files imported from Linux)

No other file in the tree has tabs why should these?

Nak, unless your intention is to immediately apply a patch converting
tabs to 8 spaces.

Interestingly, the citrix email server apears to mangle tabs and replace
them with spaces (which made the copy of these patch I received via Cc
appear to do nothing at all). Perhaps this is where it went wrong
originally?

> "git diff" and "git diff -b" vs. Stefano's v6 branch now contain the same
> output -- i.e. only the intervening development

I don't think this is particularly useful long term.

> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> 
> diff -r 7fd8f10cfd3e -r 63e88a26e1ef xen/arch/arm/dtb.S
> --- a/xen/arch/arm/dtb.S	Mon Feb 13 17:03:44 2012 +0000
> +++ b/xen/arch/arm/dtb.S	Mon Feb 13 17:26:08 2012 +0000
> @@ -1,2 +1,2 @@
> -        .section .dtb,#alloc
> -        .incbin CONFIG_DTB_FILE
> +	.section .dtb,#alloc
> +	.incbin CONFIG_DTB_FILE

This was a new file that never had tabs anywhere. No need to mess about
with it.

> diff -r 7fd8f10cfd3e -r 63e88a26e1ef xen/arch/arm/entry.S
> --- a/xen/arch/arm/entry.S	Mon Feb 13 17:03:44 2012 +0000
> +++ b/xen/arch/arm/entry.S	Mon Feb 13 17:26:08 2012 +0000
[...
> -#define SAVE_ALL                                                                                       \
> -       sub sp, #(UREGS_R8_fiq - UREGS_sp); /* SP, LR, SPSR, PC */                                      \
> -       push {r0-r12}; /* Save R0-R12 */                                                                \
> -                                                                                                       \
> -       mrs r11, ELR_hyp;               /* ELR_hyp is return address. */                                \

While your messing with whitespace. How about moving that \ to below 80
columns.

David

  reply	other threads:[~2012-02-13 18:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-13 18:03 [PATCH] arm: fixup hard tabs Ian Campbell
2012-02-13 18:26 ` David Vrabel [this message]
2012-02-13 19:09   ` Ian Campbell
2012-02-13 19:39     ` Tim Deegan
2012-02-13 19:52       ` Ian Campbell

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=4F3955D9.2020900@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=stefano.stabellini@citrix.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).