From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752977AbcEPAQK (ORCPT ); Sun, 15 May 2016 20:16:10 -0400 Received: from ozlabs.org ([103.22.144.67]:41001 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752246AbcEPAQJ (ORCPT ); Sun, 15 May 2016 20:16:09 -0400 Date: Mon, 16 May 2016 10:16:06 +1000 From: Stephen Rothwell To: Kalle Valo , David Miller , Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org Subject: linux-next: manual merge of the wireless-drivers-next tree with the net-next tree Message-ID: <20160516101606.751f9613@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Kalle, Today's linux-next merge of the wireless-drivers-next tree got a conflict in: drivers/net/wireless/intel/iwlwifi/mvm/tx.c between commit: 909b27f70643 ("Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net") from the net-next tree and commit: a525d0eab17d ("Merge tag 'iwlwifi-for-kalle-2016-05-04' of git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes") from the wireless-drivers-next tree. I fixed it up (I think that the net-next tree merge lost the changes to iwl_mvm_set_tx_cmd() associated with commit 5c08b0f5026f ("iwlwifi: mvm: don't override the rate with the AMSDU len")) 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. -- Cheers, Stephen Rothwell