Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756102Ab3JPO46 (ORCPT ); Wed, 16 Oct 2013 10:56:58 -0400 Received: from mail.us.es ([193.147.175.20]:39406 "EHLO mail.us.es" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755729Ab3JPO45 (ORCPT ); Wed, 16 Oct 2013 10:56:57 -0400 X-Qmail-Scanner-Diagnostics: from 127.0.0.1 by antivirus3 (envelope-from , uid 501) with qmail-scanner-2.10 (clamdscan: 0.98/17964. spamassassin: 3.3.2. Clear:RC:1(127.0.0.1):SA:0(-99.8/7.5):. Processed in 2.125805 secs); 16 Oct 2013 14:57:14 -0000 X-Spam-ASN: AS12715 188.78.0.0/16 X-Envelope-From: pneira@us.es Date: Wed, 16 Oct 2013 16:56:52 +0200 From: Pablo Neira Ayuso To: Jiri Kosina Cc: Jozsef Kadlecsik , Thierry Reding , Patrick McHardy , Maxime Jayat , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: linux-next: manual merge of the trivial tree Message-ID: <20131016145652.GB16959@localhost> References: <1381845763-10487-1-git-send-email-treding@nvidia.com> <1381845763-10487-2-git-send-email-treding@nvidia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 Content-Length: 1915 Lines: 47 On Wed, Oct 16, 2013 at 11:20:04AM +0200, Jiri Kosina wrote: > On Wed, 16 Oct 2013, Jozsef Kadlecsik wrote: > > > > Today's linux-next merge of the trivial tree got conflicts in > > > > > > net/netfilter/xt_set.c > > > > > > caused by commits 3f79410 (treewide: Fix common typo in "identify") and > > > bd3129f (netfilter: ipset: order matches and targets separatedly in > > > xt_set.c). > > > > > > I fixed them up (see below). Please verify that the resolution looks > > > good. > > > > I don't really get it: patch bd3129f was part of a patchset, which was > > applied to net-next and there it was complete. > > > > There's none of the patchset in question in linux-next, so what's the > > trivial tree? Where's lost what? To Jozsef: David collects all the networking patches in net-next until Linus' merge window opens, that's why you don't see your patches in linux-next. It seems Jiri merges this trivial tree (which indeed contains your net-next patches already) to linux-next. > > [The patch below doesn't look good, because it should contain the removed > > part for the revision 1 match due to the reordering in the file.] > > This is just a super-simple conflict between > > https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=bd3129f > > and > > https://git.kernel.org/cgit/linux/kernel/git/jikos/trivial.git/diff/net/netfilter/xt_set.c?h=for-next&id=3f79410c7c > > I don't think it needs any special handling, do you? I can of course drop > the respective hunk from my tree and let you handle it in net-next if you > wish. Please, don't drop it, I think Jozsef got confused by the handling of your trivial tree. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/