Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760594Ab3JPJUL (ORCPT ); Wed, 16 Oct 2013 05:20:11 -0400 Received: from cantor2.suse.de ([195.135.220.15]:53673 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760182Ab3JPJUI (ORCPT ); Wed, 16 Oct 2013 05:20:08 -0400 Date: Wed, 16 Oct 2013 11:20:04 +0200 (CEST) From: Jiri Kosina To: Jozsef Kadlecsik Cc: Thierry Reding , Pablo Neira Ayuso , Patrick McHardy , Maxime Jayat , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: linux-next: manual merge of the trivial tree In-Reply-To: Message-ID: References: <1381845763-10487-1-git-send-email-treding@nvidia.com> <1381845763-10487-2-git-send-email-treding@nvidia.com> User-Agent: Alpine 2.00 (LNX 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1478 Lines: 44 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? > > [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. Thanks, -- Jiri Kosina SUSE Labs -- 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/