From patchwork Thu Aug 27 00:34:33 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Stephen Rothwell X-Patchwork-Id: 1352191 X-Patchwork-Delegate: davem@davemloft.net Return-Path: X-Original-To: patchwork-incoming-netdev@ozlabs.org Delivered-To: patchwork-incoming-netdev@ozlabs.org Authentication-Results: ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=vger.kernel.org (client-ip=23.128.96.18; helo=vger.kernel.org; envelope-from=netdev-owner@vger.kernel.org; receiver=) Authentication-Results: ozlabs.org; dmarc=none (p=none dis=none) header.from=canb.auug.org.au Authentication-Results: ozlabs.org; dkim=pass (2048-bit key; secure) header.d=canb.auug.org.au header.i=@canb.auug.org.au header.a=rsa-sha256 header.s=201702 header.b=UFWD8x2L; dkim-atps=neutral Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by ozlabs.org (Postfix) with ESMTP id 4BcNz70cdZz9sSJ for ; Thu, 27 Aug 2020 10:34:42 +1000 (AEST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726968AbgH0Aek (ORCPT ); Wed, 26 Aug 2020 20:34:40 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39982 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726148AbgH0Aek (ORCPT ); Wed, 26 Aug 2020 20:34:40 -0400 Received: from ozlabs.org (ozlabs.org [IPv6:2401:3900:2:1::2]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D17ACC061574; Wed, 26 Aug 2020 17:34:39 -0700 (PDT) Received: from authenticated.ozlabs.org (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.ozlabs.org (Postfix) with ESMTPSA id 4BcNz009m4z9sSJ; Thu, 27 Aug 2020 10:34:35 +1000 (AEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=canb.auug.org.au; s=201702; t=1598488476; bh=9J3Z/RzmtRQDyJKD7cxNHhVKPsEKKjMqAhiaCqWxv2I=; h=Date:From:To:Cc:Subject:From; b=UFWD8x2L2olBkNTpbRRIUM7dWECWZiMc99uPAX0WIoRISLai8zFPDCV+WMnFvdtjg PBPnqHOGQuswyRV5R3QBTQ4ePO44EFHGcWbK+2bZj8ZrqvuqKSEvNtLZD5kHhfp7vs T3DAagGDrblUZXvu//6DxFHLKolN+rn3EXzAkepV9Cyau7hV4t4ZumTOqiDteRgJZQ IS64ek5kA4O5UDuct0UHeCQXd3xen99XGXPmnRSP9vJXxRM8cqU68QBONvPuIeopHe 5/BceKJjs+6D7SUCXdKQRpUZZBIGc+nargChAR+0jJg1qsE6shXKfXkrPBLmelwQZb WY82hQatXfuJQ== Date: Thu, 27 Aug 2020 10:34:33 +1000 From: Stephen Rothwell To: David Miller , Networking Cc: Linux Next Mailing List , Linux Kernel Mailing List , Mingming Cao , Dany Madden , Thomas Falcon Subject: linux-next: manual merge of the net-next tree with the net tree Message-ID: <20200827103433.43d384c8@canb.auug.org.au> MIME-Version: 1.0 Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org Hi all, Today's linux-next merge of the net-next tree got a conflict in: drivers/net/ethernet/ibm/ibmvnic.c between commit: 9f1345737790 ("ibmvnic fix NULL tx_pools and rx_tools issue at do_reset") from the net tree and commit: 507ebe6444a4 ("ibmvnic: Fix use-after-free of VNIC login response buffer") from the net-next tree. I fixed it up (see below) 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. diff --cc drivers/net/ethernet/ibm/ibmvnic.c index d3a774331afc,86a83e53dce5..000000000000 --- a/drivers/net/ethernet/ibm/ibmvnic.c