From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Rothwell Subject: Re: [PATCH v2] pstore: add lzo/lz4 compression support Date: Thu, 2 Jun 2016 09:10:40 +1000 Message-ID: <20160602091040.3892599b@canb.auug.org.au> References: <20160430022637.GA8702@localhost.localdomain> <3908561D78D1C84285E8C5FCA982C28F3A0BAF44@ORSMSX114.amr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from ozlabs.org ([103.22.144.67]:41797 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750914AbcFAXKm (ORCPT ); Wed, 1 Jun 2016 19:10:42 -0400 In-Reply-To: Sender: linux-next-owner@vger.kernel.org List-ID: To: Kees Cook Cc: Tony Luck , linux-next@vger.kernel.org Hi Kees, On Tue, 31 May 2016 12:44:04 -0700 Kees Cook wrote: > > Can you please add my pstore tree to -next? I'm taking over from Tony Luck. > > git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git#for-next/pstore Added from today. Thanks for adding your subsystem tree as a participant of linux-next. As you may know, this is not a judgement of your code. The purpose of linux-next is for integration testing and to lower the impact of conflicts between subsystems in the next merge window. You will need to ensure that the patches/commits in your tree/series have been: * submitted under GPL v2 (or later) and include the Contributor's Signed-off-by, * posted to the relevant mailing list, * reviewed by you (or another maintainer of your subsystem tree), * successfully unit tested, and * destined for the current or next Linux merge window. Basically, this should be just what you would send to Linus (or ask him to fetch). It is allowed to be rebased if you deem it necessary. -- Cheers, Stephen Rothwell sfr@canb.auug.org.au