From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joe Perches Subject: Re: linux-next: manual merge of the net-next tree with the net tree Date: Mon, 23 Mar 2015 05:55:31 -0700 Message-ID: <1427115331.16851.11.camel@perches.com> References: <20150323140841.0b807b95@canb.auug.org.au> <20150323124723.GA6740@salvia> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Return-path: Received: from smtprelay0182.hostedemail.com ([216.40.44.182]:34838 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752930AbbCWMzf (ORCPT ); Mon, 23 Mar 2015 08:55:35 -0400 In-Reply-To: <20150323124723.GA6740@salvia> Sender: linux-next-owner@vger.kernel.org List-ID: To: Pablo Neira Ayuso Cc: Stephen Rothwell , David Miller , netdev@vger.kernel.org, linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Patrick McHardy On Mon, 2015-03-23 at 13:47 +0100, Pablo Neira Ayuso wrote: > On Mon, Mar 23, 2015 at 02:08:41PM +1100, Stephen Rothwell wrote: > > Today's linux-next merge of the net-next tree got a conflict in > > net/netfilter/nf_tables_core.c between commit 4017a7ee693d ("netfilter: > > restore rule tracing via nfnetlink_log") from the net tree and commit > > 01ef16c2dd2e ("netfilter: nf_tables: minor tracing cleanups") from the > > net-next tree. > > > > I fixed it up (see below) and can carry the fix as necessary (no action > > is required). > " > This looks good, thanks for adressing this conflict Stephen. trivia: > > diff --cc net/netfilter/nf_tables_core.c [] > > + static struct nf_loginfo trace_loginfo = { > > + .type = NF_LOG_TYPE_LOG, > > + .u = { > > + .log = { > > + .level = 4, Perhaps all the .level = 4 uses should be LOGLEVEL_WARNING and .level = 5 should be LOGLEVEL_NOTICE