From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754872Ab3ARAmy (ORCPT ); Thu, 17 Jan 2013 19:42:54 -0500 Received: from out5-smtp.messagingengine.com ([66.111.4.29]:43245 "EHLO out5-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752076Ab3ARAmw (ORCPT ); Thu, 17 Jan 2013 19:42:52 -0500 X-Sasl-enc: aLc3vETyPCXZiSsjrFkVS6SfhE81Xw840Y+hhZDpHOov 1358469771 Date: Thu, 17 Jan 2013 16:42:50 -0800 From: Greg KH To: Stephen Rothwell Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Nitin Gupta , Davidlohr Bueso Subject: Re: linux-next: manual merge of the staging tree with Linus' tree Message-ID: <20130118004250.GC29380@kroah.com> References: <20130117133533.c005e3b2ee5c489e94902e3a@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130117133533.c005e3b2ee5c489e94902e3a@canb.auug.org.au> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jan 17, 2013 at 01:35:33PM +1100, Stephen Rothwell wrote: > Hi Greg, > > Today's linux-next merge of the staging tree got a conflict in > drivers/staging/zram/zram_drv.c between commit 397c60668aa5 ("staging: > zram: fix invalid memory references during disk write") from Linus' tree > and commit d178a07c4bd3 ("staging: zram: drop zram_stat_dec/inc > functions") from the staging tree. > > I fixed it up (see below) and can carry the fix as necessary (no action > is required). Looks good, thanks. greg k-h