Open Karl-opec opened 7 years ago
Yes. Keep in mind that any -next repo can be a mixture of kernel X and X+1. In kernel 4.11, the prototype for change_virtual_intf() is int (change_virtual_intf)(struct wiphy wiphy, struct net_device dev, enum nl80211_iftype type, u32 flags, struct vif_params *params);
In kernel 4.12 and already in linux-next, the prototype will change into int (change_virtual_intf)(struct wiphy wiphy, struct net_device dev, enum nl80211_iftype type, struct vif_params params);
In other words, the argument of "u32 *flags" is dropped. The same thing happens in the prototype for add_virtual_intf().
The complicated part is that the source for rtl8723bu relies on being able to use the kernel version macro to determine what form of the API we should use. I have committed the correct patch, but it will not work for you. The change required for your code would break every user of kernel 4.11. If you pull the new source, and edit the two places that mention KERNEL(4, 12, 0) by replacing the 12 with 11, then your build will work. Once you switch to a 4.12-rcX kernel, your build will fail. At that point use "git checkout -f" to remove your changes.
After succesfully compiling it for 4.11-rc6-next-20170411, compilation breaks with following Error for 4.11.0-next-2017051 on arm64:
Any Idea?