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


Groups > linux.kernel > #1446050 > unrolled thread

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

Started byStephen Rothwell <sfr@canb.auug.org.au>
First post2016-07-19 08:10 +0200
Last post2016-07-20 20:40 +0200
Articles 9 — 4 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-07-19 08:10 +0200
    Re: linux-next: build failure after merge of the wireless-drivers-next tree Kalle Valo <kvalo@codeaurora.org> - 2016-07-19 08:40 +0200
      Re: linux-next: build failure after merge of the wireless-drivers-next  tree Rafał Miłecki <zajec5@gmail.com> - 2016-07-19 09:00 +0200
        Re: linux-next: build failure after merge of the wireless-drivers-next tree Kalle Valo <kvalo@codeaurora.org> - 2016-07-19 09:10 +0200
          Re: linux-next: build failure after merge of the wireless-drivers-next  tree Rafał Miłecki <zajec5@gmail.com> - 2016-07-19 09:20 +0200
            Re: linux-next: build failure after merge of the wireless-drivers-next tree Kalle Valo <kvalo@codeaurora.org> - 2016-07-19 16:10 +0200
              Re: linux-next: build failure after merge of the  wireless-drivers-next tree Brian Norris <computersforpeace@gmail.com> - 2016-07-19 20:40 +0200
                Re: linux-next: build failure after merge of the  wireless-drivers-next tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-07-20 01:40 +0200
                Re: linux-next: build failure after merge of the wireless-drivers-next tree Kalle Valo <kvalo@codeaurora.org> - 2016-07-20 20:40 +0200

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

FromStephen Rothwell <sfr@canb.auug.org.au>
Date2016-07-19 08:10 +0200
Subjectlinux-next: build failure after merge of the wireless-drivers-next tree
Message-ID<rWwo9-lB-3@gated-at.bofh.it>
Hi all,

After merging the wireless-drivers-next tree, today's linux-next build
(powerpc allyesconfig) failed like this:

drivers/mtd/devices/bcm47xxsflash.c: In function 'bcm47xxsflash_bcma_probe':
drivers/mtd/devices/bcm47xxsflash.c:299:17: error: implicit declaration of function 'ioremap_cache' [-Werror=implicit-function-declaration]
  b47s->window = ioremap_cache(res->start, resource_size(res));
                 ^
drivers/mtd/devices/bcm47xxsflash.c:299:15: warning: assignment makes pointer from integer without a cast [-Wint-conversion]
  b47s->window = ioremap_cache(res->start, resource_size(res));
               ^

Caused by commit

  57d8f7dd2132 ("bcma: allow enabling serial flash support on non-MIPS SoCs")

I have reverted that commit for today.

-- 
Cheers,
Stephen Rothwell

[toc] | [next] | [standalone]


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

FromKalle Valo <kvalo@codeaurora.org>
Date2016-07-19 08:40 +0200
SubjectRe: linux-next: build failure after merge of the wireless-drivers-next tree
Message-ID<rWwRb-y1-1@gated-at.bofh.it>
In reply to#1446050
Stephen Rothwell <sfr@canb.auug.org.au> writes:

> After merging the wireless-drivers-next tree, today's linux-next build
> (powerpc allyesconfig) failed like this:
>
> drivers/mtd/devices/bcm47xxsflash.c: In function 'bcm47xxsflash_bcma_probe':
> drivers/mtd/devices/bcm47xxsflash.c:299:17: error: implicit declaration of function 'ioremap_cache' [-Werror=implicit-function-declaration]
>   b47s->window = ioremap_cache(res->start, resource_size(res));
>                  ^
> drivers/mtd/devices/bcm47xxsflash.c:299:15: warning: assignment makes pointer from integer without a cast [-Wint-conversion]
>   b47s->window = ioremap_cache(res->start, resource_size(res));
>                ^
>
> Caused by commit
>
>   57d8f7dd2132 ("bcma: allow enabling serial flash support on non-MIPS SoCs")
>
> I have reverted that commit for today.

Thanks, kbuild bot also notified about this.

Rafał, as the merge window is getting really close I would like to
revert this for now and we can reapply it once we the problem is fully
solved. And we can use my pending branch for build testing the patch
with kbuild bot. What do you think?

-- 
Kalle Valo

[toc] | [prev] | [next] | [standalone]


#1446080

FromRafał Miłecki <zajec5@gmail.com>
Date2016-07-19 09:00 +0200
Message-ID<rWxay-FB-29@gated-at.bofh.it>
In reply to#1446060
On 19 July 2016 at 08:30, Kalle Valo <kvalo@codeaurora.org> wrote:
> Stephen Rothwell <sfr@canb.auug.org.au> writes:
>
>> After merging the wireless-drivers-next tree, today's linux-next build
>> (powerpc allyesconfig) failed like this:
>>
>> drivers/mtd/devices/bcm47xxsflash.c: In function 'bcm47xxsflash_bcma_probe':
>> drivers/mtd/devices/bcm47xxsflash.c:299:17: error: implicit declaration of function 'ioremap_cache' [-Werror=implicit-function-declaration]
>>   b47s->window = ioremap_cache(res->start, resource_size(res));
>>                  ^
>> drivers/mtd/devices/bcm47xxsflash.c:299:15: warning: assignment makes pointer from integer without a cast [-Wint-conversion]
>>   b47s->window = ioremap_cache(res->start, resource_size(res));
>>                ^
>>
>> Caused by commit
>>
>>   57d8f7dd2132 ("bcma: allow enabling serial flash support on non-MIPS SoCs")
>>
>> I have reverted that commit for today.
>
> Thanks, kbuild bot also notified about this.
>
> Rafał, as the merge window is getting really close I would like to
> revert this for now and we can reapply it once we the problem is fully
> solved. And we can use my pending branch for build testing the patch
> with kbuild bot. What do you think?

The simplest fix sounds pretty much as simple as the revert. In the
seconds thread I was considering two fixes: switching to memremap and
adding depends on.

What about trying a simple "depends on"?

-- 
Rafał

[toc] | [prev] | [next] | [standalone]


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

FromKalle Valo <kvalo@codeaurora.org>
Date2016-07-19 09:10 +0200
SubjectRe: linux-next: build failure after merge of the wireless-drivers-next tree
Message-ID<rWxke-YG-41@gated-at.bofh.it>
In reply to#1446080
Rafał Miłecki <zajec5@gmail.com> writes:

> On 19 July 2016 at 08:30, Kalle Valo <kvalo@codeaurora.org> wrote:
>> Stephen Rothwell <sfr@canb.auug.org.au> writes:
>>
>>> After merging the wireless-drivers-next tree, today's linux-next build
>>> (powerpc allyesconfig) failed like this:
>>>
>>> drivers/mtd/devices/bcm47xxsflash.c: In function 'bcm47xxsflash_bcma_probe':
>>> drivers/mtd/devices/bcm47xxsflash.c:299:17: error: implicit declaration of function 'ioremap_cache' [-Werror=implicit-function-declaration]
>>>   b47s->window = ioremap_cache(res->start, resource_size(res));
>>>                  ^
>>> drivers/mtd/devices/bcm47xxsflash.c:299:15: warning: assignment makes pointer from integer without a cast [-Wint-conversion]
>>>   b47s->window = ioremap_cache(res->start, resource_size(res));
>>>                ^
>>>
>>> Caused by commit
>>>
>>>   57d8f7dd2132 ("bcma: allow enabling serial flash support on non-MIPS SoCs")
>>>
>>> I have reverted that commit for today.
>>
>> Thanks, kbuild bot also notified about this.
>>
>> Rafał, as the merge window is getting really close I would like to
>> revert this for now and we can reapply it once we the problem is fully
>> solved. And we can use my pending branch for build testing the patch
>> with kbuild bot. What do you think?
>
> The simplest fix sounds pretty much as simple as the revert.

The problem is that I don't have much time, I need to send the pull
request to Dave within next few days. The fix might create other
problems so I'm not enthusiastic about iterating with this patch at the
moment. I think it can wait for 4.9.

-- 
Kalle Valo

[toc] | [prev] | [next] | [standalone]


#1446145

FromRafał Miłecki <zajec5@gmail.com>
Date2016-07-19 09:20 +0200
Message-ID<rWxtV-129-43@gated-at.bofh.it>
In reply to#1446113
On 19 July 2016 at 09:09, Kalle Valo <kvalo@codeaurora.org> wrote:
> Rafał Miłecki <zajec5@gmail.com> writes:
>
>> On 19 July 2016 at 08:30, Kalle Valo <kvalo@codeaurora.org> wrote:
>>> Stephen Rothwell <sfr@canb.auug.org.au> writes:
>>>
>>>> After merging the wireless-drivers-next tree, today's linux-next build
>>>> (powerpc allyesconfig) failed like this:
>>>>
>>>> drivers/mtd/devices/bcm47xxsflash.c: In function 'bcm47xxsflash_bcma_probe':
>>>> drivers/mtd/devices/bcm47xxsflash.c:299:17: error: implicit declaration of function 'ioremap_cache' [-Werror=implicit-function-declaration]
>>>>   b47s->window = ioremap_cache(res->start, resource_size(res));
>>>>                  ^
>>>> drivers/mtd/devices/bcm47xxsflash.c:299:15: warning: assignment makes pointer from integer without a cast [-Wint-conversion]
>>>>   b47s->window = ioremap_cache(res->start, resource_size(res));
>>>>                ^
>>>>
>>>> Caused by commit
>>>>
>>>>   57d8f7dd2132 ("bcma: allow enabling serial flash support on non-MIPS SoCs")
>>>>
>>>> I have reverted that commit for today.
>>>
>>> Thanks, kbuild bot also notified about this.
>>>
>>> Rafał, as the merge window is getting really close I would like to
>>> revert this for now and we can reapply it once we the problem is fully
>>> solved. And we can use my pending branch for build testing the patch
>>> with kbuild bot. What do you think?
>>
>> The simplest fix sounds pretty much as simple as the revert.
>
> The problem is that I don't have much time, I need to send the pull
> request to Dave within next few days. The fix might create other
> problems so I'm not enthusiastic about iterating with this patch at the
> moment. I think it can wait for 4.9.

I sent a patch seconds ago, you may just take a look at it. If you
still prefer to revert my commit, go ahead.

-- 
Rafał

[toc] | [prev] | [next] | [standalone]


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

FromKalle Valo <kvalo@codeaurora.org>
Date2016-07-19 16:10 +0200
SubjectRe: linux-next: build failure after merge of the wireless-drivers-next tree
Message-ID<rWDSG-516-17@gated-at.bofh.it>
In reply to#1446145
Rafał Miłecki <zajec5@gmail.com> writes:

> On 19 July 2016 at 09:09, Kalle Valo <kvalo@codeaurora.org> wrote:
>> Rafał Miłecki <zajec5@gmail.com> writes:
>>
>>> On 19 July 2016 at 08:30, Kalle Valo <kvalo@codeaurora.org> wrote:
>>>> Stephen Rothwell <sfr@canb.auug.org.au> writes:
>>>>
>>>>> After merging the wireless-drivers-next tree, today's linux-next build
>>>>> (powerpc allyesconfig) failed like this:
>>>>>
>>>>> drivers/mtd/devices/bcm47xxsflash.c: In function 'bcm47xxsflash_bcma_probe':
>>>>> drivers/mtd/devices/bcm47xxsflash.c:299:17: error: implicit declaration of function 'ioremap_cache' [-Werror=implicit-function-declaration]
>>>>>   b47s->window = ioremap_cache(res->start, resource_size(res));
>>>>>                  ^
>>>>> drivers/mtd/devices/bcm47xxsflash.c:299:15: warning: assignment makes pointer from integer without a cast [-Wint-conversion]
>>>>>   b47s->window = ioremap_cache(res->start, resource_size(res));
>>>>>                ^
>>>>>
>>>>> Caused by commit
>>>>>
>>>>>   57d8f7dd2132 ("bcma: allow enabling serial flash support on non-MIPS SoCs")
>>>>>
>>>>> I have reverted that commit for today.
>>>>
>>>> Thanks, kbuild bot also notified about this.
>>>>
>>>> Rafał, as the merge window is getting really close I would like to
>>>> revert this for now and we can reapply it once we the problem is fully
>>>> solved. And we can use my pending branch for build testing the patch
>>>> with kbuild bot. What do you think?
>>>
>>> The simplest fix sounds pretty much as simple as the revert.
>>
>> The problem is that I don't have much time, I need to send the pull
>> request to Dave within next few days. The fix might create other
>> problems so I'm not enthusiastic about iterating with this patch at the
>> moment. I think it can wait for 4.9.
>
> I sent a patch seconds ago, you may just take a look at it. If you
> still prefer to revert my commit, go ahead.

Ok, let's try your fix. We still have few days. I applied the patch[1]
to the pending branch this morning and if I don't see any errors I apply
it later tonight and hopefully it will be in tomorrow's linux-next
build. Thanks for the quick fix, very much appreciated.

[1] "mtd: add arch dependency for MTD_BCM47XXSFLASH symbol"
    https://patchwork.kernel.org/patch/9236053/

-- 
Kalle Valo

[toc] | [prev] | [next] | [standalone]


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

FromBrian Norris <computersforpeace@gmail.com>
Date2016-07-19 20:40 +0200
SubjectRe: linux-next: build failure after merge of the wireless-drivers-next tree
Message-ID<rWI5Y-7uZ-29@gated-at.bofh.it>
In reply to#1446506
Just to head this off, since I noticed it...

On Tue, Jul 19, 2016 at 05:08:59PM +0300, Kalle Valo wrote:
> Rafał Miłecki <zajec5@gmail.com> writes:
> > I sent a patch seconds ago, you may just take a look at it. If you
> > still prefer to revert my commit, go ahead.
> 
> Ok, let's try your fix. We still have few days. I applied the patch[1]
> to the pending branch this morning and if I don't see any errors I apply
> it later tonight and hopefully it will be in tomorrow's linux-next
> build. Thanks for the quick fix, very much appreciated.
> 
> [1] "mtd: add arch dependency for MTD_BCM47XXSFLASH symbol"
>     https://patchwork.kernel.org/patch/9236053/

I applied a trivial change to this same Kconfig entry:

Subject: mtd: update description of MTD_BCM47XXSFLASH symbol
http://git.infradead.org/l2-mtd.git/commitdiff/0a526341fee054c1e2b9f0e4b2b424ae81707d4c

It's a trivial conflict, so should we just let Linus work it out? I can
note it my MTD pull request, if wireless lands first.

Brian

[toc] | [prev] | [next] | [standalone]


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

FromStephen Rothwell <sfr@canb.auug.org.au>
Date2016-07-20 01:40 +0200
SubjectRe: linux-next: build failure after merge of the wireless-drivers-next tree
Message-ID<rWMMh-1Zy-3@gated-at.bofh.it>
In reply to#1446659
Hi Brian,

On Tue, 19 Jul 2016 11:39:13 -0700 Brian Norris <computersforpeace@gmail.com> wrote:
>
> I applied a trivial change to this same Kconfig entry:
> 
> Subject: mtd: update description of MTD_BCM47XXSFLASH symbol
> http://git.infradead.org/l2-mtd.git/commitdiff/0a526341fee054c1e2b9f0e4b2b424ae81707d4c
> 
> It's a trivial conflict, so should we just let Linus work it out? I can
> note it my MTD pull request, if wireless lands first.

Linus and I should be able to cope.  I will send my usual notification today.

-- 
Cheers,
Stephen Rothwell

[toc] | [prev] | [next] | [standalone]


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

FromKalle Valo <kvalo@codeaurora.org>
Date2016-07-20 20:40 +0200
SubjectRe: linux-next: build failure after merge of the wireless-drivers-next tree
Message-ID<rX4zw-4Ze-21@gated-at.bofh.it>
In reply to#1446659
Brian Norris <computersforpeace@gmail.com> writes:

> Just to head this off, since I noticed it...
>
> On Tue, Jul 19, 2016 at 05:08:59PM +0300, Kalle Valo wrote:
>> Rafał Miłecki <zajec5@gmail.com> writes:
>> > I sent a patch seconds ago, you may just take a look at it. If you
>> > still prefer to revert my commit, go ahead.
>> 
>> Ok, let's try your fix. We still have few days. I applied the patch[1]
>> to the pending branch this morning and if I don't see any errors I apply
>> it later tonight and hopefully it will be in tomorrow's linux-next
>> build. Thanks for the quick fix, very much appreciated.
>> 
>> [1] "mtd: add arch dependency for MTD_BCM47XXSFLASH symbol"
>>     https://patchwork.kernel.org/patch/9236053/
>
> I applied a trivial change to this same Kconfig entry:
>
> Subject: mtd: update description of MTD_BCM47XXSFLASH symbol
> http://git.infradead.org/l2-mtd.git/commitdiff/0a526341fee054c1e2b9f0e4b2b424ae81707d4c
>
> It's a trivial conflict, so should we just let Linus work it out? I can
> note it my MTD pull request, if wireless lands first.

Sounds good to me. Do note that Linus doesn't pull wireless-drivers-next
directly, it goes through net-next. But I'll let Dave also know about
this when I send him the pull request.

-- 
Kalle Valo

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web