Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964862AbWLTDuS (ORCPT ); Tue, 19 Dec 2006 22:50:18 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964865AbWLTDuS (ORCPT ); Tue, 19 Dec 2006 22:50:18 -0500 Received: from smtp.osdl.org ([65.172.181.25]:60062 "EHLO smtp.osdl.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964862AbWLTDuQ (ORCPT ); Tue, 19 Dec 2006 22:50:16 -0500 Date: Tue, 19 Dec 2006 19:49:31 -0800 From: Andrew Morton To: Randy Dunlap Cc: David Brownell , Matthew Garrett , Arjan van de Ven , linux-kernel@vger.kernel.org, gregkh@suse.de Subject: Re: Changes to sysfs PM layer break userspace Message-Id: <20061219194931.e2527895.akpm@osdl.org> In-Reply-To: <20061219183539.70bd3e9e.randy.dunlap@oracle.com> References: <20061219185223.GA13256@srcf.ucam.org> <1166559785.3365.1276.camel@laptopd505.fenrus.org> <20061219203251.GA14648@srcf.ucam.org> <200612191334.49760.david-b@pacbell.net> <20061219181524.c15c02af.akpm@osdl.org> <20061219183539.70bd3e9e.randy.dunlap@oracle.com> X-Mailer: Sylpheed version 2.2.7 (GTK+ 2.8.17; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1317 Lines: 39 On Tue, 19 Dec 2006 18:35:39 -0800 Randy Dunlap wrote: > On Tue, 19 Dec 2006 18:15:24 -0800 Andrew Morton wrote: > > > On Tue, 19 Dec 2006 13:34:49 -0800 > > David Brownell wrote: > > > > > Documentation/feature-removal-schedule.txt has warned about this since > > > August > > > > Nobody reads that. > > Ugh, I read it. > > > Please, wherever possible, put a nice printk("this is going away") in the code > > when planning these things. > > Can notices go in both places, or is in the source code (printk) > now the preferred way? I think printks grab a lot more attention. It's not surprising that people get surprised when the feature they're using goes away. Plus they may not even know that that they're using the feature. A printk fixes that. > I think that we can point people to Doc/feature-removal-schedule.txt > easier (and more effectively) than we can source code (or noisy kernel > logs). Hopefully developers who see the printk will think to look in feature-removal-schedule.txt for more details. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/