From: Bart Van Assche <bvanassche@acm.org>
To: Rong Chen <rong.a.chen@intel.com>,
kbuild test robot <lkp@intel.com>,
Alexander Duyck <alexander.h.duyck@linux.intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
gregkh@linuxfoundation.org, linux-nvdimm@lists.01.org,
tj@kernel.org, akpm@linux-foundation.org,
linux-pm@vger.kernel.org, jiangshanlai@gmail.com,
rafael@kernel.org, len.brown@intel.com, pavel@ucw.cz,
zwisler@kernel.org, dan.j.williams@intel.com,
dave.jiang@intel.com
Subject: Re: [driver-core PATCH v5 5/9] driver core: Establish clear order of operations for deferred probe and remove
Date: Fri, 23 Nov 2018 06:19:53 -0800 [thread overview]
Message-ID: <f9ccdf33-6b7a-cdb2-150b-3ab83892c96e@acm.org> (raw)
In-Reply-To: <d70f2bcb-0e1c-2d69-2692-329ef5cf81bc@intel.com>
On 11/22/18 5:23 PM, Rong Chen wrote:
> 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'"
Hi Rong,
Thanks for having taken a look. That's indeed something that must be
fixed in patch 5/9.
Bart.
next prev parent reply other threads:[~2018-11-23 14:19 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 4/9] driver core: Move async_synchronize_full call Alexander Duyck
[not found] ` <154145231976.29224.39638353241256116.stgit-+uVpp3jiz/RcxmDmkzA3yGt3HXsI98Cx0E9HWUfgJXw@public.gmane.org>
2018-11-06 1:04 ` Bart Van Assche
[not found] ` <1541466289.196084.176.camel-HInyCGIudOg@public.gmane.org>
2018-11-06 16:18 ` Alexander Duyck
[not found] ` <e2fec0e159757f31abbd258e284a844d0d8a2859.camel-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2018-11-06 17:22 ` Bart Van Assche
[not found] ` <154145223352.29224.8912797012647157172.stgit-+uVpp3jiz/RcxmDmkzA3yGt3HXsI98Cx0E9HWUfgJXw@public.gmane.org>
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
[not found] ` <154145230445.29224.14651284855380723028.stgit-+uVpp3jiz/RcxmDmkzA3yGt3HXsI98Cx0E9HWUfgJXw@public.gmane.org>
2018-11-06 0:42 ` Bart Van Assche
[not found] ` <1541464948.196084.168.camel-HInyCGIudOg@public.gmane.org>
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
[not found] ` <154145230954.29224.13087735653265580553.stgit-+uVpp3jiz/RcxmDmkzA3yGt3HXsI98Cx0E9HWUfgJXw@public.gmane.org>
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:12 ` [driver-core PATCH v5 5/9] driver core: Establish clear order of operations for deferred probe and remove Alexander Duyck
[not found] ` <154145232484.29224.1635232599636954462.stgit-+uVpp3jiz/RcxmDmkzA3yGt3HXsI98Cx0E9HWUfgJXw@public.gmane.org>
2018-11-06 4:10 ` kbuild test robot
[not found] ` <201811061228.iteFLO2p%fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2018-11-06 23:51 ` Bart Van Assche
2018-11-07 0:52 ` Alexander Duyck
[not found] ` <1541548274.196084.197.camel-HInyCGIudOg@public.gmane.org>
2018-11-23 1:23 ` Rong Chen
2018-11-23 14:19 ` Bart Van Assche [this message]
2018-11-06 23:48 ` Bart Van Assche
[not found] ` <1541548114.196084.195.camel-HInyCGIudOg@public.gmane.org>
2018-11-07 1:34 ` Joe Perches
[not found] ` <499e4358e72fca510fa6fcfb76ea3ac3792db08f.camel-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
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
[not found] ` <154145232994.29224.4383053368766089653.stgit-+uVpp3jiz/RcxmDmkzA3yGt3HXsI98Cx0E9HWUfgJXw@public.gmane.org>
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
[not found] ` <154145233508.29224.9891071445860629874.stgit-+uVpp3jiz/RcxmDmkzA3yGt3HXsI98Cx0E9HWUfgJXw@public.gmane.org>
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
[not found] ` <154145234017.29224.9183571187943571535.stgit-+uVpp3jiz/RcxmDmkzA3yGt3HXsI98Cx0E9HWUfgJXw@public.gmane.org>
2018-11-07 0:24 ` Bart Van Assche
2018-11-06 0:50 ` [driver-core PATCH v5 0/9] Add NUMA aware async_schedule calls Bart Van Assche
[not found] ` <1541465425.196084.170.camel-HInyCGIudOg@public.gmane.org>
2018-11-06 16:25 ` Alexander Duyck
2018-11-05 21:12 ` [driver-core PATCH v5 9/9] libnvdimm: Schedule device registration on node local to the device Alexander Duyck
[not found] ` <154145234526.29224.2575533246153120029.stgit-+uVpp3jiz/RcxmDmkzA3yGt3HXsI98Cx0E9HWUfgJXw@public.gmane.org>
2018-11-07 0:26 ` Bart Van Assche
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=f9ccdf33-6b7a-cdb2-150b-3ab83892c96e@acm.org \
--to=bvanassche@acm.org \
--cc=akpm@linux-foundation.org \
--cc=alexander.h.duyck@linux.intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--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=rong.a.chen@intel.com \
--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).