Received: by 10.192.165.148 with SMTP id m20csp5062920imm; Tue, 8 May 2018 21:22:22 -0700 (PDT) X-Google-Smtp-Source: AB8JxZrjJSihef75D+zlcOFQB7mOmjih10l6Ry6F6YtbaWheHtG5FEgv44MyWy0ja11VMDuTPo2x X-Received: by 2002:a65:5504:: with SMTP id f4-v6mr20116533pgr.177.1525839742392; Tue, 08 May 2018 21:22:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525839742; cv=none; d=google.com; s=arc-20160816; b=g67zufrIuPUcwKL6l+T0CH6iKF6apG0Icb+qBgnfzcPbaDXXdEvo4PwmzjwvjL7Sol YVRpXudj40VULJvISpUz3s8OgEm/Yg9eoHUO3YLc6fS/hJ9njCogiHM5osEBgVlbSNi+ FFSJNmSVJJyWLgl1A96T9gAAdiefWXBTSQhMeFJtC8D9qCSzYAKXXgrH6KuOgpQXNxfE lybcZBk7w6ddfX0FGeUp6xWw/GSl2DD7/RFioBdp0MmGkYu1cBtTERcJJ4ii+94eOBCZ p9P5Go09lpazgfNkGaGfOvrmYVQJstlVUJhXvZB16JXox+awGvj54nV0jpuCK8irNOyv bjpA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:dkim-signature :arc-authentication-results; bh=RUqRtnu3FE4GtFwC2gEqpnpXRtI7RWe06Ca0vd/AwDs=; b=lfdln/dieBt43t/BtRku789R7PRjyytm7OSV3XQ1QbU+XVPmYHSbSUuils7gp2E3YN f++OnOvCAhQkKhG6aq1LMmaC8YUwa3tDnqCDBFlnwxo9BsiEr2i91wp2+FhbgYFK7h8J J/M0AqrEFx+48TncSN/gxxNTtd5hjJrDTj1qo7B5rRYBQ3XhkuWc3Z70wYf/sNeaKCPD YfeXBYrHQTi2fwK2AM3XVf6MHAKkkN8eAj70xK4LpygBx/nTYpsoLpJ4BTUfYSsxvLU1 yA78RIB4NSMM1er4A8vZsMlJHnNL7n53QhccUwlqloRa2ZKAxQdvkXhNNjzn0NaYbhHg zmIw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@canb.auug.org.au header.s=201702 header.b=D5xBSEk7; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e11-v6si14466068pgu.274.2018.05.08.21.22.07; Tue, 08 May 2018 21:22:22 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@canb.auug.org.au header.s=201702 header.b=D5xBSEk7; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933511AbeEIEV6 (ORCPT + 99 others); Wed, 9 May 2018 00:21:58 -0400 Received: from ozlabs.org ([203.11.71.1]:46985 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751000AbeEIEV4 (ORCPT ); Wed, 9 May 2018 00:21:56 -0400 Received: from authenticated.ozlabs.org (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ozlabs.org (Postfix) with ESMTPSA id 40gjqQ6RhTz9s3Z; Wed, 9 May 2018 14:21:54 +1000 (AEST) Authentication-Results: ozlabs.org; dmarc=none (p=none dis=none) header.from=canb.auug.org.au DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=canb.auug.org.au; s=201702; t=1525839715; bh=WeH/H2xfPE7WHcjxyzWun7udVjebJEsPwKmBnhmnLv0=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=D5xBSEk7pqbzlaAcQQXLFPX7+o/F70kNSOcgsG0itwuDOUqpt8xwcShiUd6Cft38V 6qQxsThKP54TSSvNV+PKtfCL4zXo0CAD+1fFxlyGVvPm78KRizbdfe/JNcGQNBqudn sUhgmPQuGYik3duy5Uqum8oixyJpaUZ4MtSUZKiE40amW3uuBQtUWlg/pGSv7u8Ya5 EyTRn1UwHsozai87r0qzO7evQ6StrZNH7ShHfFYxJWofqvB7dXrYu1FeRfs9Ed4+gs XLb7wbhujDontS407dMCwB2xJNhHzLrC0nWX2LNZiWkVrwC+gjvwUCl4xoOuTTrv3+ hg8HoRBM0Cfjg== Date: Wed, 9 May 2018 14:21:54 +1000 From: Stephen Rothwell To: Networking , Martin Schwidefsky , Heiko Carstens , David Miller Cc: Daniel Borkmann , Alexei Starovoitov , Linux-Next Mailing List , Linux Kernel Mailing List Subject: Re: linux-next: manual merge of the bpf-next tree with the s390 tree Message-ID: <20180509142154.73ff5772@canb.auug.org.au> In-Reply-To: <20180508102638.1e19b7f2@canb.auug.org.au> References: <20180508102638.1e19b7f2@canb.auug.org.au> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/ZEI8h3kHyu3upTWz_00lbu/"; protocol="application/pgp-signature" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --Sig_/ZEI8h3kHyu3upTWz_00lbu/ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi all, On Tue, 8 May 2018 10:26:38 +1000 Stephen Rothwell w= rote: > > Today's linux-next merge of the bpf-next tree got a conflict in: >=20 > arch/s390/net/bpf_jit.S >=20 > between commit: >=20 > de5cb6eb514e ("s390: use expoline thunks in the BPF JIT") >=20 > from the s390 tree and commit: >=20 > e1cf4befa297 ("bpf, s390x: remove ld_abs/ld_ind") >=20 > from the bpf-next tree. >=20 > I fixed it up (I just removed the file as the latter does) and can > carry the fix as necessary. This is now fixed as far as linux-next is > concerned, but any non trivial conflicts should be mentioned to your > upstream maintainer when your tree is submitted for merging. You may > also want to consider cooperating with the maintainer of the conflicting > tree to minimise any particularly complex conflicts. This is now a conflict between the net-next and s390 trees. --=20 Cheers, Stephen Rothwell --Sig_/ZEI8h3kHyu3upTWz_00lbu/ Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAlryd2IACgkQAVBC80lX 0GxO0Af/WFqKfLIxODePDRc7kJDTY44CC0jXkQCc5YiGInrk9zBSBMGrhLZUpSv9 Vfgt+EA/r98zfpCDFwg+PJ7q6WIzRK6CnP1p8O+twQjXI+CQlJFr+4s/hAJ7KfYQ /RQauRNEJge4hfxqk8JEUjeO+yY9LNUzzHf4Pb9TJN7jt/kImBRHFPpZ+RU6uQf8 jeNk/1UtGujazY9Ys0K4ZWwbbET5cKBuMQcWJMWeyC6hT3u68JhM9b+EK0upv9A3 66OT0AwBkNqI2PWi2paA2hyxyPjljhZFIPiiW5ceMXx4m1Dg6AYFbWyHEZVgakY1 zhLJHZW5e1dgdcer733VqMS6ukJxfw== =ZCsq -----END PGP SIGNATURE----- --Sig_/ZEI8h3kHyu3upTWz_00lbu/--