From: Alexander Duyck <alexander.duyck@gmail.com>
To: bvanassche@acm.org
Cc: kbuild test robot <lkp@intel.com>,
alexander.h.duyck@linux.intel.com, len.brown@intel.com,
linux-nvdimm@lists.01.org, Greg KH <gregkh@linuxfoundation.org>,
linux-pm@vger.kernel.org, jiangshanlai@gmail.com,
LKML <linux-kernel@vger.kernel.org>,
kbuild-all@01.org, pavel@ucw.cz, zwisler@kernel.org,
Tejun Heo <tj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
rafael@kernel.org
Subject: Re: [driver-core PATCH v5 5/9] driver core: Establish clear order of operations for deferred probe and remove
Date: Tue, 6 Nov 2018 16:52:45 -0800 [thread overview]
Message-ID: <CAKgT0Ue61y6qMH3sKH6-M_eHy4Lc5p6k27LFXwmVooAL48KyYQ@mail.gmail.com> (raw)
In-Reply-To: <1541548274.196084.197.camel@acm.org>
On Tue, Nov 6, 2018 at 3:51 PM Bart Van Assche <bvanassche@acm.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
next prev parent reply other threads:[~2018-11-07 0:52 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 21:11 [driver-core PATCH v5 0/9] Add NUMA aware async_schedule calls Alexander Duyck
2018-11-05 21:11 ` [driver-core PATCH v5 1/9] workqueue: Provide queue_work_node to queue work near a given NUMA node Alexander Duyck
2018-11-06 0:42 ` Bart Van Assche
2018-11-06 16:27 ` Alexander Duyck
2018-11-05 21:11 ` [driver-core PATCH v5 2/9] async: Add support for queueing on specific " Alexander Duyck
2018-11-07 0:50 ` Bart Van Assche
2018-11-05 21:11 ` [driver-core PATCH v5 3/9] device core: Consolidate locking and unlocking of parent and device Alexander Duyck
2018-11-05 21:11 ` [driver-core PATCH v5 4/9] driver core: Move async_synchronize_full call Alexander Duyck
2018-11-06 1:04 ` Bart Van Assche
2018-11-06 16:18 ` Alexander Duyck
2018-11-06 17:22 ` Bart Van Assche
2018-11-05 21:12 ` [driver-core PATCH v5 5/9] driver core: Establish clear order of operations for deferred probe and remove Alexander Duyck
2018-11-06 4:10 ` kbuild test robot
2018-11-06 23:51 ` Bart Van Assche
2018-11-07 0:52 ` Alexander Duyck [this message]
2018-11-23 1:23 ` Rong Chen
2018-11-23 14:19 ` Bart Van Assche
2018-11-06 23:48 ` Bart Van Assche
2018-11-07 1:34 ` Joe Perches
2018-11-08 23:42 ` Bart Van Assche
2018-11-11 14:31 ` Pavel Machek
2018-11-27 2:35 ` Dan Williams
2018-11-27 16:49 ` Alexander Duyck
2018-11-05 21:12 ` [driver-core PATCH v5 6/9] driver core: Probe devices asynchronously instead of the driver Alexander Duyck
2018-11-07 0:22 ` Bart Van Assche
2018-11-05 21:12 ` [driver-core PATCH v5 7/9] driver core: Attach devices on CPU local to device node Alexander Duyck
2018-11-07 0:24 ` Bart Van Assche
2018-11-05 21:12 ` [driver-core PATCH v5 8/9] PM core: Use new async_schedule_dev command Alexander Duyck
2018-11-07 0:24 ` Bart Van Assche
2018-11-05 21:12 ` [driver-core PATCH v5 9/9] libnvdimm: Schedule device registration on node local to the device Alexander Duyck
2018-11-07 0:26 ` Bart Van Assche
2018-11-06 0:50 ` [driver-core PATCH v5 0/9] Add NUMA aware async_schedule calls Bart Van Assche
2018-11-06 16:25 ` Alexander Duyck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKgT0Ue61y6qMH3sKH6-M_eHy4Lc5p6k27LFXwmVooAL48KyYQ@mail.gmail.com \
--to=alexander.duyck@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.h.duyck@linux.intel.com \
--cc=bvanassche@acm.org \
--cc=gregkh@linuxfoundation.org \
--cc=jiangshanlai@gmail.com \
--cc=kbuild-all@01.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linux-pm@vger.kernel.org \
--cc=lkp@intel.com \
--cc=pavel@ucw.cz \
--cc=rafael@kernel.org \
--cc=tj@kernel.org \
--cc=zwisler@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).