[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170608125737.1e09c36d@canb.auug.org.au>
Date: Thu, 8 Jun 2017 12:57:37 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Igor Mitsyanko <igor.mitsyanko.os@...ntenna.com>
Cc: Kalle Valo <kvalo@...eaurora.org>,
Wireless <linux-wireless@...r.kernel.org>,
David Miller <davem@...emloft.net>,
Networking <netdev@...r.kernel.org>,
Linux-Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Dmitrii Lebed <dlebed@...ntenna.com>,
Sergei Maksimenko <smaksimenko@...ntenna.com>,
Sergey Matyukevich <smatyukevich@...ntenna.com>,
Bindu Therthala <btherthala@...ntenna.com>,
Huizhao Wang <hwang@...ntenna.com>,
Kamlesh Rath <krath@...ntenna.com>,
Avinash Patil <avinashp@...ntenna.com>
Subject: Re: linux-next: build failure after merge of the
wireless-drivers-next tree
Hi Igor,
On Wed, 7 Jun 2017 19:43:18 -0700 Igor Mitsyanko <igor.mitsyanko.os@...ntenna.com> wrote:
>
> thanks. As I understand, you've applied this patch during a merge and no
> further actions are required, correct?
Dave Miller will need to apply that patch (or something similar) when
he merges the wireless-drivers-next tree into the net-next tree. I
will keep applying the patch each day until then.
--
Cheers,
Stephen Rothwell
Powered by blists - more mailing lists