Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263038AbUCMC40 (ORCPT ); Fri, 12 Mar 2004 21:56:26 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263039AbUCMC40 (ORCPT ); Fri, 12 Mar 2004 21:56:26 -0500 Received: from gate.crashing.org ([63.228.1.57]:5337 "EHLO gate.crashing.org") by vger.kernel.org with ESMTP id S263038AbUCMC4W (ORCPT ); Fri, 12 Mar 2004 21:56:22 -0500 Subject: Re: Dealing with swsusp vs. pmdisk From: Benjamin Herrenschmidt To: "Theodore Ts'o" Cc: Pavel Machek , Andrew Morton , torvalds@transmeta.com, Linux Kernel list In-Reply-To: <20040313004756.GB5115@thunk.org> References: <20040312224645.GA326@elf.ucw.cz> <20040313004756.GB5115@thunk.org> Content-Type: text/plain Message-Id: <1079146273.1967.63.camel@gaston> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Sat, 13 Mar 2004 13:51:13 +1100 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 990 Lines: 24 > Pavel, what do you think of the swsusp2 patch, BTW? My biggest > complaint about it is that since it's maintained outside of the > kernel, it's constantly behind about 0.75 revisions behind the latest > 2.6 release. The feature set of swsusp2, if they can ever get it > completely bugfree(tm) is certainly impressive. I'd like it to be merged upstream too. It may have problems, rough edges, whatever, but keeping out of tree is more or less a guarantee that none of us will look & fix them ;) If it gets upstream, I'll gladly finish the pmac support for it that I quickly hacked recently for pmdisk as a proof of concept and help figure out some of the remaining problems. I don't feel like doing that with an out-of-tree project. Ben - 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/