From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934682AbcHaNKl (ORCPT ); Wed, 31 Aug 2016 09:10:41 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:37226 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934200AbcHaNKj (ORCPT ); Wed, 31 Aug 2016 09:10:39 -0400 Date: Wed, 31 Aug 2016 15:10:48 +0200 From: Greg Kroah-Hartman To: Ben Hutchings Cc: linux-kernel@vger.kernel.org, CT kernel Subject: Re: [PATCH] driver core: Add deferred_probe attribute to devices in sysfs Message-ID: <20160831131048.GA32056@kroah.com> References: <1471354458.1960.9.camel@codethink.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1471354458.1960.9.camel@codethink.co.uk> User-Agent: Mutt/1.7.0 (2016-08-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 16, 2016 at 02:34:18PM +0100, Ben Hutchings wrote: > It is sometimes useful to know that a device is on the deferred probe > list rather than, say, not having a driver available. Expose this > information to user-space. What can someone use this for? It's an attribute that for 99.9% of the time will always be the same value. I can see when debugging it might be nice, but what can a user do with this? thanks, greg k-h