Hi Kbuild Test Robot Guys,

On Thu, Jan 28, 2016 at 12:08 AM, Rafał Miłecki <[email protected]> wrote:
> On 27 January 2016 at 13:27, Kalle Valo <[email protected]> wrote:
>> kbuild test robot <[email protected]> writes:
>>
>>> Hi Rafał,
>>>
>>> [auto build test ERROR on wireless-drivers/master]
>>> [also build test ERROR on v4.5-rc1 next-20160125]
>>> [if your patch is applied to the wrong git tree, please drop us a note to 
>>> help improving the system]
>>>
>>> url:    
>>> https://github.com/0day-ci/linux/commits/Rafa-Mi-ecki/brcmfmac-support-for-new-14e43-4365-card-with-BCM4366/20160127-010149
>>> base:   
>>> https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers.git 
>>> master
>>> config: x86_64-allmodconfig (attached as .config)
>>> reproduce:
>>>         # save the attached .config to linux build tree
>>>         make ARCH=x86_64
>>>
>>> All errors (new ones prefixed by >>):
>>>
>>>    drivers/net/wireless/broadcom/brcm80211/brcmfmac/chip.c: In function 
>>> 'brcmf_chip_get_pmu':
>>>>> drivers/net/wireless/broadcom/brcm80211/brcmfmac/chip.c:1143:25: error: 
>>>>> 'BCMA_CC_CAP_EXT_AOB_PRESENT' undeclared (first use in this function)
>>>          pub->cc_caps_ext & BCMA_CC_CAP_EXT_AOB_PRESENT) {
>>>                             ^
>>>    drivers/net/wireless/broadcom/brcm80211/brcmfmac/chip.c:1143:25: note: 
>>> each undeclared identifier is reported only once for each function it 
>>> appears in
>>
>> I think this error was as expected because this set depends on "bcma:
>> support PMU present as separated bus core" which is not yet applied.
>
> Yes, builbot simply couldn't know about this, but I should have reply
> to make it clear I guess.

Is there any way to communicate to the test robot that this series
depends on some other series or patch?

Thanks,

-- 
Julian Calaby

Email: [email protected]
Profile: http://www.google.com/profiles/julian.calaby/
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to