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  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:	Sun, 4 Jan 2015 21:26:59 +0000
From:	Russell King - ARM Linux <>
To:	Nicolas Pitre <>
Cc:	Linus Torvalds <>,
	Pavel Machek <>,
	Marc Zyngier <>,
	kernel list <>
Subject: Re: [PATCH] Revert 9fc2105aeaaf56b0cf75296a84702d0f9e64437b to fix
 pyaudio (and probably more)

On Sun, Jan 04, 2015 at 04:20:57PM -0500, Nicolas Pitre wrote:
> On Sun, 4 Jan 2015, Linus Torvalds wrote:
> > On Sun, Jan 4, 2015 at 12:56 PM, Nicolas Pitre <> wrote:
> > >
> > > It wasted a lot of people's time before by simply being there and wrong
> > > before it was removed.  It's only a matter of whose time you want to
> > > waste.  Really.
> > 
> > Really. Shut up.
> > 
> > The whole "no regressions" thing is very much about the fact that we
> > don't waste users time.
> I was talking about users time all along.
> Never mind.  I'm sorry for the NAK and sorry for attempting to start a 
> discussion to find a better replacement.


I encourage you *not* to back down like this.  Linus is right in so far
as the regressions issue, but he is *totally* wrong to do the revert,
which IMHO has been done out of nothing more than spite.

Either *with or without* the revert, the issue still remains, and needs
to be addressed properly.

With the revert in place, we now have insanely small bogomips values
reported via /proc/cpuinfo when hardware timers are used.  That needs

FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists