From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Subject: Re: linux-next: manual merge of the staging tree with the net-next tree Date: Wed, 29 May 2013 17:03:21 +0900 Message-ID: <20130529080320.GA2961@kroah.com> References: <20130529141422.f0ce7703d21d02b9d2543930@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20130529141422.f0ce7703d21d02b9d2543930@canb.auug.org.au> Sender: linux-kernel-owner@vger.kernel.org To: Stephen Rothwell Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Jiri Pirko , David Miller , netdev@vger.kernel.org, =?utf-8?B?IlTDvGxpbiDEsHplciI=?= List-Id: linux-next.vger.kernel.org On Wed, May 29, 2013 at 02:14:22PM +1000, Stephen Rothwell wrote: > Hi Greg, > > Today's linux-next merge of the staging tree got a conflict in > drivers/staging/silicom/bpctl_mod.c between commit 351638e7deee ("net: > pass info struct via netdevice notifier") from the net-next tree and > commit f84b075178b4 ("Staging: silicom: Fixed error 'do not initialise > statics to 0 or NULL'") from the staging tree. > > I fixed it up (see below) and can carry the fix as necessary (no action > is required). The fix looks great, thanks. greg k-h