mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Jesper Nilsson <jesper.nilsson@axis.com>
Subject: Re: [PATCH 03/23] cris: introduce asm/swab.h
Date: Tue, 6 Jan 2009 13:59:17 -0800 (PST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0901061357150.3057@localhost.localdomain> (raw)
In-Reply-To: <1231277446.964.260.camel@brick>



On Tue, 6 Jan 2009, Harvey Harrison wrote:
>
> cris holds its arch overrides in an arch/ folder, rename these
> byteorder.h files to swab.h and include them from asm/swab.h
> 
> Signed-off-by: Harvey Harrison <harvey.harrison@gmail.com>
> ---
>  arch/cris/include/arch-v10/arch/byteorder.h |   28 ---------------------------
>  arch/cris/include/arch-v10/arch/swab.h      |   28 +++++++++++++++++++++++++++
>  arch/cris/include/arch-v32/arch/byteorder.h |   22 ---------------------
>  arch/cris/include/arch-v32/arch/swab.h      |   22 +++++++++++++++++++++


Since you'e a git user, and you're basically renaming files while then 
putting a new name in place, can you please send patches done with both 
the "-M" flag (rename detection) _and_ the "-B" flag (which breaks 
associations of files even if the name stays the same)?

It's rare that this is needed, but it really helps. Now the patches look 
like a big delete/create event, and it's not at all obvious that the code 
is actually the same before and after.

		Linus

  reply	other threads:[~2009-01-06 21:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-06 21:30 Harvey Harrison
2009-01-06 21:59 ` Linus Torvalds [this message]
2009-01-06 22:04   ` Harvey Harrison
2009-01-06 22:11     ` Linus Torvalds
2009-01-06 22:19       ` Sam Ravnborg
2009-01-06 22:21       ` Harvey Harrison

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.00.0901061357150.3057@localhost.localdomain \
    --to=torvalds@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=harvey.harrison@gmail.com \
    --cc=jesper.nilsson@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®