Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759320AbZKZLI1 (ORCPT ); Thu, 26 Nov 2009 06:08:27 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1759054AbZKZLI0 (ORCPT ); Thu, 26 Nov 2009 06:08:26 -0500 Received: from verein.lst.de ([213.95.11.210]:43841 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758915AbZKZLI0 (ORCPT ); Thu, 26 Nov 2009 06:08:26 -0500 Date: Thu, 26 Nov 2009 12:08:12 +0100 From: Christoph Hellwig To: anderson@redhat.com Cc: linux-kernel@vger.kernel.org, fedora-kernel@redhat.com Subject: crash driver in fedora Message-ID: <20091126110812.GA29452@lst.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i X-Spam-Score: -0.349 () BAYES_30 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 467 Lines: 11 Hi Dave, is there a good reason the crash driver is still only stuck in the Fedora kernel instead of beeing upstream? We already have the restrictive memory device options upstream, so there should be a use case for it. -- 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/