[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f9ccdf33-6b7a-cdb2-150b-3ab83892c96e@acm.org>
Date: Fri, 23 Nov 2018 06:19:53 -0800
From: Bart Van Assche <bvanassche@....org>
To: Rong Chen <rong.a.chen@...el.com>,
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/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.
Powered by blists - more mailing lists