On Thu, Apr 26, 2018 at 1:25 PM, kbuild test robot <l...@intel.com> wrote:
> Hi Arnd,
>
> I love your patch! Perhaps something to improve:
>
> [auto build test WARNING on v4.17-rc2]
> [cannot apply to sound/for-next asoc/for-next arm-soc/for-next next-20180426]
> [if your patch is applied to the wrong git tree, please drop us a note to 
> help improve the system]
>
> url:    
> https://github.com/0day-ci/linux/commits/Baolin-Wang/Fix-year-2038-issue-for-sound-subsystem/20180426-010145
> reproduce:
>         # apt-get install sparse
>         make ARCH=x86_64 allmodconfig
>         make C=1 CF=-D__CHECK_ENDIAN__
>
>
> sparse warnings: (new ones prefixed by >>)
>
>    sound/firewire/motu/motu-pcm.c:35:29: sparse: expression using sizeof(void)
>    sound/firewire/motu/motu-pcm.c:35:29: sparse: expression using sizeof(void)
>    sound/firewire/motu/motu-pcm.c:36:29: sparse: expression using sizeof(void)
>    sound/firewire/motu/motu-pcm.c:36:29: sparse: expression using sizeof(void)
>    sound/firewire/motu/motu-pcm.c:65:32: sparse: expression using sizeof(void)
>    sound/firewire/motu/motu-pcm.c:65:32: sparse: expression using sizeof(void)
>    sound/firewire/motu/motu-pcm.c:66:32: sparse: expression using sizeof(void)
>    sound/firewire/motu/motu-pcm.c:66:32: sparse: expression using sizeof(void)
>    sound/firewire/motu/motu-pcm.c:92:36: sparse: expression using sizeof(void)
>    sound/firewire/motu/motu-pcm.c:92:36: sparse: expression using sizeof(void)
>    sound/firewire/motu/motu-pcm.c:93:36: sparse: expression using sizeof(void)
>    sound/firewire/motu/motu-pcm.c:93:36: sparse: expression using sizeof(void)
>>> sound/firewire/motu/motu-pcm.c:204:50: sparse: restricted snd_pcm_state_t 
>>> degrades to integer
>    sound/firewire/motu/motu-pcm.c:223:50: sparse: restricted snd_pcm_state_t 
> degrades to integer
>    sound/firewire/motu/motu-pcm.c:238:50: sparse: restricted snd_pcm_state_t 
> degrades to integer
>    sound/firewire/motu/motu-pcm.c:254:50: sparse: restricted snd_pcm_state_t 
> degrades to integer

>From what I can tell, these are all existing driver problems, no idea why we 
>now
have one more warning than before.

       Arnd

Reply via email to