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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200803281314.53653.david-b@pacbell.net>
Date:	Fri, 28 Mar 2008 13:14:52 -0700
From:	David Brownell <david-b@...bell.net>
To:	Jan Engelhardt <jengelh@...putergmbh.de>
Cc:	Ingo Molnar <mingo@...e.hu>, Mark Lord <lkml@....ca>,
	David Miller <davem@...emloft.net>, jkosina@...e.cz,
	gregkh@...e.de, linux-kernel@...r.kernel.org,
	linux-usb@...r.kernel.org, pavel@...e.cz,
	akpm@...ux-foundation.org, rtc-linux@...glegroups.com
Subject: Re: 2.6.25-rc7: Ugh.

On Friday 28 March 2008, Jan Engelhardt wrote:
> > 	If we think that an approach is superior (which
> > your new RTC code certainly is), we have to take up the responsibility
> > of pushing that as a prominent, default choice and excluding the old
> > code. That ends up benefiting everyone, reduces complexity of the
> > kernel. You wont see anyone shed tears for the old code.
> 
> Users with audio-related usage patterns do, as SND_RTCTIMER
> still depends on old rtc :-/

-ENOPATCH :)

Last time this specific issue came up, a related point was
that the relevant ALSA documentation in this area needed
updating too.  ISTR it assumed there was only one kind of
RTC, and had a few other issues.

- Dave

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