Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 4 Dec 2002 11:03:31 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 4 Dec 2002 11:03:31 -0500 Received: from svr-ganmtc-appserv-mgmt.ncf.coxexpress.com ([24.136.46.5]:37386 "EHLO svr-ganmtc-appserv-mgmt.ncf.coxexpress.com") by vger.kernel.org with ESMTP id ; Wed, 4 Dec 2002 11:03:31 -0500 Subject: Re: [PATCH] deprecate use of bdflush() From: Robert Love To: Krzysztof Halasa Cc: linux-kernel@vger.kernel.org In-Reply-To: References: <1038935401.994.9.camel@phantasy> <3DED0076.55B970DD@yahoo.com> Content-Type: text/plain Organization: Message-Id: <1039018264.1509.3.camel@phantasy> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.0 Date: 04 Dec 2002 11:11:04 -0500 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 763 Lines: 21 On Tue, 2002-12-03 at 20:12, Krzysztof Halasa wrote: > So why don't we print the warning with 2.4 as well? We should of. Now its too late - we cannot start printing evil warnings on existing 2.4 systems. > I don't know if returning -EINVAL (= removing the call completely in 2.5) > isn't better, though - does it have any compatibility implications? Right now the call forces a do_exit(), so the application terminates. If we just returned `-EINVAL' the application might sit around doing nothing. Robert Love - 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/