linux-kernel - Re: {NOT a PATCH} Corrections please ...

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, 21 Aug 2008 12:47:43 -0700
From:	Kevin Diggs <kevdig@...ersurf.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Stefan Richter <stefanr@...6.in-berlin.de>,
	linux-kernel@...r.kernel.org, david@...morbit.com, arnd@...db.de,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: {NOT a PATCH} Corrections please ...

Ingo Molnar wrote:
> * Kevin Diggs <kevdig@...ersurf.com> wrote:
> 
> 
>>Here is the latest (maybe line wrap is set to 99 so it won't be goofed 
>>anymore?):
> 
> 
> the patch wont apply as it has whitespace corruption (double spaces). 
> Please check Documentation/email-clients.txt.
> 
> 	Ingo
> 
> 
The double spacing between the diffs? That will prevent it from applying?

I'm still just trying to get the content correct.

Who should this patch be sent to when it is ready? Also, I think I remember
reading in submitting patches that patches should be cced to the general
linux-kernel list. This correct?

kevin
--
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/