linux-kernel - Re: [PATCH 2/2] FRV: Move to arch/frv/include/asm/

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 9 Apr 2009 16:31:38 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	David Howells <dhowells@...hat.com>
cc:	Andrew Morton <akpm@...ux-foundation.org>, sam@...nborg.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/2] FRV: Move to arch/frv/include/asm/

On Fri, 10 Apr 2009, David Howells wrote:
>
> Move arch headers from include/asm-frv/ to arch/frv/include/asm/.

David, please _look_ at your patches before sending them out.

Sure, you got the diffstat/summary right, but look at the patch itself - 
it doesn't actually match what you claimed to send out, and has it all as 
file creates/deletes, and so your email is - once more - over half a meg 
in size.

Yes, yes, I can apply it, and it will all end up being the same thing, but 
what I'm looking for is the knowledge that you can send out proper 
patches, so that future file moves don't have this. So I don't want to 
apply it before I know that the process works. Right now it doesn't.

		Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/