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, 17 Jan 2008 23:22:42 +0100 (CET)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Kyle McMartin <kyle@...artin.ca>
cc:	mingo@...e.hu,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: x86: remove casts


On Jan 17 2008 01:43, Kyle McMartin wrote:
>On Wed, Jan 16, 2008 at 11:57:54PM +0100, Jan Engelhardt wrote:
>> 
>> On Jan 16 2008 17:20, Kyle McMartin wrote:
>> >On Wed, Jan 16, 2008 at 10:15:39PM +0100, Jan Engelhardt wrote:
>> >> parent a9f7faa5fd229a65747f02ab0f2d45ee35856760
>> >> commit ffffffffffffffffffffffffffffffffffffffff
>> >
>> >^- did you just make that up? ;-)
>> 
>> Yes. git does not care anyway.
>> 
>
>right. the point was if you had generated a sha1 of all ones. that would
>be kind of neat.
>
Should have used 0000.. because that is what git uses if there is
'nothing' (e.g. "from 0000.." on git-push).
I decided to nuke the commit id because the patch does not match
the one in my uploaded git tree anymore; and issuing a merge seems
like overkill for x86, so i just sent a cherry patch like this.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ