Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1397730

Re: linux-next: manual merge of the net-next tree with the wireless-drivers tree

From Kalle Valo <kvalo@codeaurora.org>
Newsgroups linux.kernel
Subject Re: linux-next: manual merge of the net-next tree with the wireless-drivers tree
Date 2016-05-10 08:50 +0200
Message-ID <rx9Et-5o7-1@gated-at.bofh.it> (permalink)
References <rwHoR-YK-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Stephen Rothwell <sfr@canb.auug.org.au> writes:

> Today's linux-next merge of the net-next tree got a conflict in:
>
>   drivers/net/wireless/intel/iwlwifi/mvm/tx.c
>
> between commit:
>
>   5c08b0f5026f ("iwlwifi: mvm: don't override the rate with the AMSDU len")
>
> from the wireless-drivers tree and commit:
>
>   d8fe484470dd ("iwlwifi: mvm: add support for new TX CMD API")
>
> 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.

I'm planning to fix this by merging wireless-drivers to
wireless-drivers-next later today and most likely tomorrow send a
wireless-drivers-next pull request to Dave.

-- 
Kalle Valo

Back to linux.kernel | Previous | NextPrevious in thread | Find similar | Unroll thread


Thread

linux-next: manual merge of the net-next tree with the  wireless-drivers tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-05-09 02:40 +0200
  Re: linux-next: manual merge of the net-next tree with the wireless-drivers tree Kalle Valo <kvalo@codeaurora.org> - 2016-05-10 08:50 +0200

csiph-web