[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87o9532zld.fsf@kamboji.qca.qualcomm.com>
Date: Thu, 18 Apr 2019 16:49:02 +0300
From: Kalle Valo <kvalo@...eaurora.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Wireless <linux-wireless@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Shahar S Matityahu <shahar.s.matityahu@...el.com>,
Luca Coelho <luciano.coelho@...el.com>
Subject: Re: linux-next: manual merge of the wireless-drivers-next tree with the wireless-drivers tree
Stephen Rothwell <sfr@...b.auug.org.au> writes:
> Hi all,
>
> Today's linux-next merge of the wireless-drivers-next tree got a conflict
> in:
>
> drivers/net/wireless/intel/iwlwifi/iwl-trans.h
>
> between commit:
>
> 07d35b4270ef ("iwlwifi: use sync nmi in case of init flow failure")
>
> from the wireless-drivers tree and commit:
>
> 4b1831e48974 ("iwlwifi: dbg_ini: support HW error trigger")
>
> from the wireless-drivers-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.
Thanks, I'll let Dave know about this when he pulls w-d-next.
--
Kalle Valo
Powered by blists - more mailing lists