[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170608224725.6cd98500@canb.auug.org.au>
Date: Thu, 8 Jun 2017 22:47:25 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Kalle Valo <kvalo@...eaurora.org>
Cc: Igor Mitsyanko <igor.mitsyanko.os@...ntenna.com>,
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 Kalle,
On Thu, 08 Jun 2017 15:07:00 +0300 Kalle Valo <kvalo@...eaurora.org> wrote:
>
> Stephen Rothwell <sfr@...b.auug.org.au> writes:
>
> > 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.
>
> Thanks, I'll remind Dave about this when i submit the pull request (very
> soon now).
It occurred to me just after I wrote the previous message that it would
only be true after he merges the current net tree into the net-next tree.
--
Cheers,
Stephen Rothwell
Powered by blists - more mailing lists