Received: by 2002:a05:6a10:f3d0:0:0:0:0 with SMTP id a16csp569396pxv; Thu, 8 Jul 2021 08:55:20 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyDi4UTL6ui+YkdRitJxGdR3eNQ8zztX0MUmDnmTp79O4iiGw+dbQkvjm0VH7wtVUTi9Qtf X-Received: by 2002:aa7:c3d5:: with SMTP id l21mr39278128edr.62.1625759720673; Thu, 08 Jul 2021 08:55:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1625759720; cv=none; d=google.com; s=arc-20160816; b=XXQxRIohEAM0YdWeGeeRausVoQSMveN+2KWHDYiIcGerYN0sZqHiN013j44rJ3ZZEN lcplwxdSFgJBIa9d5ACVXnHQWLI13IUKh2GGZQokpx+ejRf43MxnsrIn263lR/s55fSs uTcmU4ZNx/5JvXPteJNfj6aejvuhg+3MucRhJArj25CrWMoXf3y7v5O9udvgrdvjLmPN DNqCJNGEihxcY4t2HPi5TDwRtpyukXnr4L686OS5Lk3oKQOoQht69nrx2ld+VqBucp3t MHMcaN0NJ7HpO3lcl1NNeaXd6ELQbVepsCHDVh2/ZWLUyXAvppHRNSopLkrAQhGilp43 GhmQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=dFlMQBGO31V9098Ic+58x9aN6qNtiKn44dnxlMTsibk=; b=nf9VzEUgoApzT50/Yg2KL9qjqpgZvzKdiPx0F5P/k9043NU0u9jGZ1pmZe6PhKn7i0 qMKhiliDwVdVfO6D7Etdu3KOt26KGnmGcWgT48HXHR4UH5Zu/ojQg3L1h6/h7052j23Z j4Nq5HWNsNm++4D3IUg/VSenkrBB6KLZFLjSTmNiJeie7M82DaOFtKTPY+N838ssZYy0 Mv5vWWGMSeXOFSw+jgyNWGIY7OFo1J1rh1O4c3mzbWJBVlfqVnQW3/CAJuLO3nnDlOxH K7uuWJUX4/1Jy95uFr50KXhichMbyvlQR7Ualxkwh+YqEu5LHY4G95B2gdAKXEwPiXoX kXfw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=YCVWy7FR; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id 27si3285671eja.1.2021.07.08.08.54.56; Thu, 08 Jul 2021 08:55:20 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=YCVWy7FR; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232010AbhGHP4q (ORCPT + 99 others); Thu, 8 Jul 2021 11:56:46 -0400 Received: from mail.kernel.org ([198.145.29.99]:60422 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229592AbhGHP4p (ORCPT ); Thu, 8 Jul 2021 11:56:45 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id C656161607; Thu, 8 Jul 2021 15:54:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1625759642; bh=v8x9Y1LFn397E4RLSsmhaYisK4hXaBItCKmaYE2nS+8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=YCVWy7FRlMlhuufwP4E30YPUOr0NoJAH37e9WUCvsz/VIHruAZfBqYThUJ7Tgxo9e EqJsEXW+Iz4SzGWJUKae8PepgLg/lP14zPj8PBhHIJRZlwS7GG+yf5R61RWKsRw1Ax VEqsR5mj8UcSE9oPsLbgica2qfXt+zNk6/1i8F6A= Date: Thu, 8 Jul 2021 17:53:59 +0200 From: Greg Kroah-Hartman To: Wenchao Hao Cc: "Rafael J . Wysocki" , linux-kernel@vger.kernel.org, linfeilong@huawei.com, Wu Bo , Zhiqiang Liu Subject: Re: [PATCH] driver core: Make probe_type of driver accessible via sysfs Message-ID: References: <20210708122010.262510-1-haowenchao@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org A: http://en.wikipedia.org/wiki/Top_post Q: Were do I find info about this thing called top-posting? A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? A: No. Q: Should I include quotations after my reply? http://daringfireball.net/2007/07/on_top On Thu, Jul 08, 2021 at 08:49:31PM +0800, Wenchao Hao wrote: > In some scenarios, you need to know whether the probe() callback in struct > driver which triggered by device_add() or driver_register() is called > synchronous or not, and modify this mode according to user requirements. Who needs to know this? What can you modify that will change anything? What will you do to change it that will solve a problem that just fixing the driver would not solve instead? And what are these magic numbers that probe_type is? If they are exported to userspace, shouldn't they be a string instead? > While kernel now does not open an interface for users to query or > modify, so I add this interface. You need to really document this in the changelog text, and in the abi documentation, otherwise we have no idea what this for. thanks, greg k-h