Re: randconfig build error with next-20140520, in drivers/staging/rtl8723au/core/rtw_cmd.c

[Jes Sorensen]

Jim Davis <jim.epost@xxxxxxxxx> writes:
> Building with the attached random configuration file,
>
> drivers/staging/rtl8723au/core/rtw_cmd.c: In function âdynamic_chk_wk_hdlâ:
> drivers/staging/rtl8723au/core/rtw_cmd.c:1036:2: error: implicit declaration of
> function ârtl8723a_sreset_xmit_status_checkâ [-Werror=implicit-function-declarat
> ion]
>   rtl8723a_sreset_xmit_status_check(padapter);
>   ^
> drivers/staging/rtl8723au/core/rtw_cmd.c:1041:2: error: implicit declaration of
> function ârtl8723a_HalDmWatchDogâ [-Werror=implicit-function-declaration]
>   rtl8723a_HalDmWatchDog(padapter);
>   ^
> drivers/staging/rtl8723au/core/rtw_cmd.c: In function âc2h_evt_hdlâ:
> drivers/staging/rtl8723au/core/rtw_cmd.c:1314:4: error: implicit
> declaration of function âc2h_handler_8723aâ
> [-Werror=implicit-function-declaration]
>     ret = c2h_handler_8723a(adapter, c2h_evt);
>     ^
> drivers/staging/rtl8723au/core/rtw_cmd.c: In function ârtw_evt_workâ:
> drivers/staging/rtl8723au/core/rtw_cmd.c:1348:2: error: implicit
> declaration of function âc2h_id_filter_ccx_8723aâ
> [-Werror=implicit-function-declaration]
>   if (c2h_id_filter_ccx_8723a(ework->u.c2h_evt.id) == true) {
>   ^
>   CC      drivers/staging/rtl8188eu/hal/HalHWImg8188E_MAC.o
> cc1: some warnings being treated as errors
> make[3]: *** [drivers/staging/rtl8723au/core/rtw_cmd.o] Error 1

Jim,

Thanks for the report.

I already pushed a fix for the CONFIG_8723AU_BT_COEXIST=n problem, and
the CONFIG_8723AU_AP_MODE=n case isn't causing build problems in my tree
at this point. I believe this is due to moving a number of functions
around. There were some warnings about unused functions which I fixed up
here, but nothing breaking the build.

If you don't mind, I prefer to push it all out with my next batch of
changes rather than trying to fix up this build case.

Cheers,
Jes
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/