Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751817AbXB0Uam (ORCPT ); Tue, 27 Feb 2007 15:30:42 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751816AbXB0Uam (ORCPT ); Tue, 27 Feb 2007 15:30:42 -0500 Received: from smtp.osdl.org ([65.172.181.24]:50538 "EHLO smtp.osdl.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751805AbXB0Uak (ORCPT ); Tue, 27 Feb 2007 15:30:40 -0500 Date: Tue, 27 Feb 2007 12:26:34 -0800 From: Andrew Morton To: "Mike Miller (OS Dev)" Cc: jens.axboe@oracle.com, linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org, gregkh@novell.com Subject: Re: [Patch 2/2] cciss: supercedes add shutdown support (replaces reboot notifier) Message-Id: <20070227122634.324fc8b1.akpm@linux-foundation.org> In-Reply-To: <20070223204239.GA10570@beardog.cca.cpqcorp.net> References: <20070223204239.GA10570@beardog.cca.cpqcorp.net> X-Mailer: Sylpheed version 2.2.4 (GTK+ 2.8.19; i686-pc-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: 1648 Lines: 36 > On Fri, 23 Feb 2007 14:42:39 -0600 "Mike Miller (OS Dev)" wrote: > This patch supercedes yesterdays cciss-shutdown patch. The primary difference is > removing __devexit from cciss_remove_one. Instead of create another function I'd > rather use the code that was intended to perform the cleanup and cache flush. I've > tested as a loadable module and statically linked without error. > Please consider this for inclusion. Please don't document patches like this. The entirety of your changelog and the Subject: are relative to a patch which will never hit the mainline git tree. Put yourself in the position of someone reading the git changelogs in a year's time. They're going to be left scratching their heads at the above, aren't they? Always include a complete and standalone, not-referential-to-an-old-patch changelog in each iteration of a patch. Always choose a suitable Subject: Yes, it's good to tell us things about how this patch differs from the previous one. That info can be placed after the ^--- which comes after your signed-off-by:, or can be placed at the top of the email, as long as the full permanent changelog is there too. Bottom line: you are submitting code and its documentation into the permanent kernel record, not just the mailing list. Try to make it appropriate, thanks. Please send a new Subject: and changlog for this patch. - 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/