From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933335AbdKBJdB (ORCPT ); Thu, 2 Nov 2017 05:33:01 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:49428 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932190AbdKBJdA (ORCPT ); Thu, 2 Nov 2017 05:33:00 -0400 Date: Thu, 2 Nov 2017 10:33:12 +0100 From: Greg Kroah-Hartman To: Adrian Hunter Cc: "Rafael J. Wysocki" , linux-kernel Subject: Re: [PATCH] driver core: Fix device link deferred probe Message-ID: <20171102093312.GB16369@kroah.com> References: <1509614573-29850-1-git-send-email-adrian.hunter@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1509614573-29850-1-git-send-email-adrian.hunter@intel.com> User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Nov 02, 2017 at 11:22:53AM +0200, Adrian Hunter wrote: > A device probe deferred because of a device link is never probed again > because it is not added to the deferred_probe_pending_list. Add it, taking > care of the race with driver_deferred_probe_trigger(). What hardware is triggering this? Is this a new thing, or something that has always happened? thanks, greg k-h