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


Groups > linux.kernel > #1337772 > unrolled thread

linux-next: build failure after merge of the wireless-drivers-next tree

Started byStephen Rothwell <sfr@canb.auug.org.au>
First post2016-02-19 00:20 +0100
Last post2016-02-19 09:10 +0100
Articles 2 — 2 participants

Back to article view | Back to linux.kernel


Contents

  linux-next: build failure after merge of the wireless-drivers-next  tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-02-19 00:20 +0100
    Re: linux-next: build failure after merge of the wireless-drivers-next tree Kalle Valo <kvalo@codeaurora.org> - 2016-02-19 09:10 +0100

#1337772 — linux-next: build failure after merge of the wireless-drivers-next tree

FromStephen Rothwell <sfr@canb.auug.org.au>
Date2016-02-19 00:20 +0100
Subjectlinux-next: build failure after merge of the wireless-drivers-next tree
Message-ID<r3G1B-4rC-37@gated-at.bofh.it>
Hi Kalle,

After merging the wireless-drivers-next tree, today's linux-next build
failed the same way as the net-next tree did yesterday (suprise! :-)).

I have used the version from next-20160218 for today.

-- 
Cheers,
Stephen Rothwell

[toc] | [next] | [standalone]


#1337952 — Re: linux-next: build failure after merge of the wireless-drivers-next tree

FromKalle Valo <kvalo@codeaurora.org>
Date2016-02-19 09:10 +0100
SubjectRe: linux-next: build failure after merge of the wireless-drivers-next tree
Message-ID<r3Oiu-24t-13@gated-at.bofh.it>
In reply to#1337772
Stephen Rothwell <sfr@canb.auug.org.au> writes:

> After merging the wireless-drivers-next tree, today's linux-next build
> failed the same way as the net-next tree did yesterday (suprise! :-)).
>
> I have used the version from next-20160218 for today.

Yeah, not a surprise as yesterday I fast forwarded wireless-drivers-next
to current net-next (at the time). I understood from the discussion in
the other thread that this commit should fix it:

376471a7b6e9 bnx2x: Add missing HSI for big-endian machines

I now fast forwarded wireless-next-next again and it contains the commit
so everything should be ok again, I hope :) If not, please let me know.

-- 
Kalle Valo

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web