From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754233AbbDGQyf (ORCPT ); Tue, 7 Apr 2015 12:54:35 -0400 Received: from mail-pd0-f178.google.com ([209.85.192.178]:36781 "EHLO mail-pd0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751122AbbDGQya (ORCPT ); Tue, 7 Apr 2015 12:54:30 -0400 MIME-Version: 1.0 In-Reply-To: <20150407132136.23da9e91@canb.auug.org.au> References: <20150407132136.23da9e91@canb.auug.org.au> Date: Tue, 7 Apr 2015 09:54:29 -0700 Message-ID: Subject: Re: linux-next: manual merge of the net-next tree with the net tree From: Cong Wang To: Stephen Rothwell Cc: David Miller , Linux Kernel Network Developers , linux-next@vger.kernel.org, LKML , "Eric W. Biederman" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Apr 6, 2015 at 8:21 PM, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the net-next tree got a conflict in > net/core/fib_rules.c between commit 419df12fb5fa ("net: move > fib_rules_unregister() under rtnl lock") from the net tree and commit > efd7ef1c1929 ("net: Kill hold_net release_net") from the net-next tree. > > I fixed it up (see below) and can carry the fix as necessary (no action > is required). > Looks correct to me. Thanks!