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:	Fri, 3 Feb 2012 22:42:27 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Jesper Juhl <jj@...osbits.net>
Cc:	Steven Rostedt <rostedt@...dmis.org>, linux-kernel@...r.kernel.org,
	Ingo Molnar <mingo@...hat.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Arjan van de Ven <arjan@...ux.intel.com>
Subject: Re: [PATCH][Trivial] Fix up version number reference in
 include/trace/events/power.h

On Sun, 15 Jan 2012, Jesper Juhl wrote:

> > > -/* This code will be removed after deprecation time exceeded (2.6.41) */
> > > +/* This code will be removed after deprecation time exceeded (3.1) */
> > 
> > Shouldn't the real fix be to remove this code? What's the use of
> > changing the version number that this code will be removed from, when
> > the change won't get in until after the version that this code should
> > have been removed?
> > 
> > This is like updating 2014 calendars to say the world will end in 2012.
> > 
> Heh, yeah, in a way you are right. But we have lots of code in the kernel 
> that says it will be removed at <some date in the past>, so I just figured 
> that if this code ends up hanging around it should at least display the 
> correct version number for when it /should/ have been removed.
> The actual removal I'll leave up to others.

Funny thing. Okay, this doesn't seem to be in linux-next, so I am taking 
it.

Steven, planning to drop the code in a near future? :)

-- 
Jiri Kosina
SUSE Labs
--
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