[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKgT0Ue61y6qMH3sKH6-M_eHy4Lc5p6k27LFXwmVooAL48KyYQ@mail.gmail.com>
Date: Tue, 6 Nov 2018 16:52:45 -0800
From: Alexander Duyck <alexander.duyck@...il.com>
To: bvanassche@....org
Cc: kbuild test robot <lkp@...el.com>,
alexander.h.duyck@...ux.intel.com, len.brown@...el.com,
linux-nvdimm@...ts.01.org, Greg KH <gregkh@...uxfoundation.org>,
linux-pm@...r.kernel.org, jiangshanlai@...il.com,
LKML <linux-kernel@...r.kernel.org>, kbuild-all@...org,
pavel@....cz, zwisler@...nel.org, Tejun Heo <tj@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>, rafael@...nel.org
Subject: Re: [driver-core PATCH v5 5/9] driver core: Establish clear order of
operations for deferred probe and remove
On Tue, Nov 6, 2018 at 3:51 PM Bart Van Assche <bvanassche@....org> 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.
It isn't a bug. It is pointing out the same thing you did. I didn't
document the async_probe value so it added a warning to the list.
>> include/linux/device.h:1056: warning: Function parameter or member 'async_probe' not described in 'device'
I'll fix it for the next version.
- Alex
Powered by blists - more mailing lists