[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d70f2bcb-0e1c-2d69-2692-329ef5cf81bc@intel.com>
Date: Fri, 23 Nov 2018 09:23:47 +0800
From: Rong Chen <rong.a.chen@...el.com>
To: Bart Van Assche <bvanassche@....org>,
kbuild test robot <lkp@...el.com>,
Alexander Duyck <alexander.h.duyck@...ux.intel.com>
Cc: kbuild-all@...org, linux-kernel@...r.kernel.org,
gregkh@...uxfoundation.org, linux-nvdimm@...ts.01.org,
tj@...nel.org, akpm@...ux-foundation.org, linux-pm@...r.kernel.org,
jiangshanlai@...il.com, rafael@...nel.org, len.brown@...el.com,
pavel@....cz, zwisler@...nel.org, dan.j.williams@...el.com,
dave.jiang@...el.com
Subject: Re: [driver-core PATCH v5 5/9] driver core: Establish clear order of
operations for deferred probe and remove
On 11/07/2018 07:51 AM, Bart Van Assche wrote:
> On Tue, 2018-11-06 at 12:10 +0800, kbuild test robot wrote:
>> Hi Alexander,
>>
>> Thank you for the patch! Perhaps something to improve:
>>
>> [auto build test WARNING on driver-core/master]
>>
>> url: https://github.com/0day-ci/linux/commits/Alexander-Duyck/Add-NUMA-aware-async_schedule-calls/20181106-093800
>> reproduce: make htmldocs
>>
>> All warnings (new ones prefixed by >>):
>>
>> include/net/mac80211.h:1001: warning: Function parameter or member 'status.is_valid_ack_signal' not described in 'ieee80211_tx_info'
>> [ ... ]
> There are plenty of references in this report to header files not touched
> by patch 5/9 in this series. I assume that this report indicates a bug in
> the 0-day testing infrastructure?
>
> Bart.
>
Hi Bart,
Kbuild robot printed all warnings and the below warning was found in
patch 5/9.
"include/linux/device.h:1056: warning: Function parameter or member
'async_probe' not described in 'device'"
Best Regards,
Rong Chen
Powered by blists - more mailing lists