[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1541548274.196084.197.camel@acm.org>
Date: Tue, 06 Nov 2018 15:51:14 -0800
From: Bart Van Assche <bvanassche@....org>
To: 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 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.
Powered by blists - more mailing lists