Hi Douglas,

[auto build test ERROR on next-20160120]
[cannot apply to v4.4-rc8 v4.4-rc7 v4.4-rc6 v4.4]
[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/Douglas-Anderson/usb-dwc2-host-Fix-and-speed-up-all-the-stuff-especially-with-splits/20160121-131414
config: x86_64-randconfig-x019-01201142 (attached as .config)
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

   In file included from drivers/usb/dwc2/core.c:57:0:
>> drivers/usb/dwc2/hcd.h:345:44: error: 'DWC2_HS_SCHEDULE_UFRAMES' undeclared 
>> here (not in a function)
     struct dwc2_hs_transfer_time hs_transfers[DWC2_HS_SCHEDULE_UFRAMES];
                                               ^
   drivers/usb/dwc2/core.c: In function 'dwc2_hc_start_transfer':
   drivers/usb/dwc2/core.c:1964:17: error: 'struct dwc2_hsotg' has no member 
named 'split_order'
              &hsotg->split_order);
                    ^
--
   In file included from drivers/usb/dwc2/core_intr.c:54:0:
>> drivers/usb/dwc2/hcd.h:345:44: error: 'DWC2_HS_SCHEDULE_UFRAMES' undeclared 
>> here (not in a function)
     struct dwc2_hs_transfer_time hs_transfers[DWC2_HS_SCHEDULE_UFRAMES];
                                               ^

vim +/DWC2_HS_SCHEDULE_UFRAMES +345 drivers/usb/dwc2/hcd.h

   339          u16 device_us;
   340          u16 host_interval;
   341          u16 device_interval;
   342          u16 next_active_frame;
   343          u16 start_active_frame;
   344          s16 num_hs_transfers;
 > 345          struct dwc2_hs_transfer_time 
 > hs_transfers[DWC2_HS_SCHEDULE_UFRAMES];
   346          u32 ls_start_schedule_slice;
   347          u16 ntd;
   348          struct list_head qtd_list;

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

Attachment: .config.gz
Description: Binary data

Reply via email to