From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: linux-next: manual merge of the net-next tree with Linus' tree Date: Mon, 22 Apr 2013 20:41:34 -0400 (EDT) Message-ID: <20130422.204134.24585943335801567.davem@davemloft.net> References: <20130422124334.92adfce6bdbcba7b08fe83a2@canb.auug.org.au> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from shards.monkeyblade.net ([149.20.54.216]:40684 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753338Ab3DWAlf (ORCPT ); Mon, 22 Apr 2013 20:41:35 -0400 In-Reply-To: <20130422124334.92adfce6bdbcba7b08fe83a2@canb.auug.org.au> Sender: linux-next-owner@vger.kernel.org List-ID: To: sfr@canb.auug.org.au Cc: netdev@vger.kernel.org, linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, ivecera@redhat.com, kaber@trash.net From: Stephen Rothwell Date: Mon, 22 Apr 2013 12:43:34 +1000 > Today's linux-next merge of the net-next tree got a conflict in > drivers/net/ethernet/emulex/benet/be_main.c between commit f11a869d4e38 > ("be2net: take care of __vlan_put_tag return value") from Linus' tree and > commit 86a9bad3ab6b ("net: vlan: add protocol argument to packet tagging > functions") from the net-next tree. > > I fixed it up (see below) and can carry the fix as necessary (no action > is required). I took care of this during the net --> net-next merge, thanks!