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] [day] [month] [year] [list]
Date:	Thu, 23 Apr 2015 15:12:03 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Rasmus Villemoes <linux@...musvillemoes.dk>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
	linux-kernel@...r.kernel.org, "H.J. Lu" <hjl.tools@...il.com>
Subject: Re: [PATCH] x86_64: use -mskip-rax-setup when available

On Thu, Apr 23, 2015 at 02:55:02PM +0200, Rasmus Villemoes wrote:
> I think we're talking past each other. What I'd like credit for is
> coming up with the idea of omitting the xor %eax,%eax in the first place
> (the original mail was sent to x86@...nel.org [cc'ed to a few x86
> maintainers], but that doesn't seem to be publicly archived).

Ok, now *this* I was missing. I'll add that information to the commit
message.

> Agreed - all I ask for is being mentioned somewhere in the commit
> log. Again, I only sent the April 20 patch because I hadn't seen
> anything happen since December.

Right, and I think situations like that can be much easier handled in
the future by you or the person who's interested in the patch, replying
to the original submission and asking what the status is instead of
doing a new and identical patch.

We're on the same page now :-)

Thanks!

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--
--
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