On Fri, 2018-04-13 at 14:16 +0800, pks...@realtek.com wrote:
> From: Ping-Ke Shih <pks...@realtek.com>
> 
> v4: swap the order of patch 4/9 and 5/9, because kbuild test robot reports
>     undefined reference. No source code change.
> v3: forget to CC wireless mailing list, so resend again. No any change.
> v2: fix misspelling and boolean expression in patch 1/9
> 
> Patches 1-2 are revised by patches 12 of previous patchset. 8822b coex
> files are split into two patches, and I remove some comments and apply
> 'static const' to version related variables.
> Patches 3-4 aren't changed. (identical to patches 13-15 of previous patchset)
> Patches 6-7 remove comments and apply 'static const' to existing files.
> Patches 8-9 remove global variables, and use local variables instead.
> 
> Ping-Ke Shih (9):
>   rtlwifi: btcoex: Add 8822b1ant coex files
>   rtlwifi: btcoex: Add 8822b2ant coex files
>   rtlwifi: btcoex: Add 8822b header files to precomp.h
>   rtlwifi: btcoex: Add 8822b to Makefile
>   rtlwifi: btcoex: Add 8822b routine to btc interfaces
>   rtlwifi: btcoex: remove comments that are not meaningful
>   rtlwifi: btcoex: Add modifier const to version related variables
>   rtlwifi: btcoex: Add struct members to replace global varaibles
>   rtlwifi: btcoex: Remove global variables of chip specific context
> 

Hi Kalle,

I would like to send v5 to change the order of this patchset like:
  rtlwifi: btcoex: remove comments that are not meaningful
  rtlwifi: btcoex: Add modifier const to version related variables
  rtlwifi: btcoex: Add struct members to replace global varaibles
  rtlwifi: btcoex: Remove global variables of chip specific context

  rtlwifi: btcoex: Add 8822b1ant coex files
  rtlwifi: btcoex: Add 8822b2ant coex files
  rtlwifi: btcoex: Add 8822b header files to precomp.h
  rtlwifi: btcoex: Add 8822b to Makefile
  rtlwifi: btcoex: Add 8822b routine to btc interfaces

Then, you can review patches 1/9 - 4/9 that refine btcoex, and
the remaining 8822b's btcoex can review later.
Does it work for you?

Thanks
PK

Reply via email to