Received: by 2002:a05:6a10:9afc:0:0:0:0 with SMTP id t28csp162066pxm; Wed, 2 Mar 2022 12:32:02 -0800 (PST) X-Google-Smtp-Source: ABdhPJxI1GffEKcMwbHYwzWgR+bkg9K9y3Fy0yYbbWe4dehsvtjgZcyKAm9jcW0PEywKTiEDJ/B9 X-Received: by 2002:a50:d097:0:b0:415:cec5:3b31 with SMTP id v23-20020a50d097000000b00415cec53b31mr1645536edd.377.1646253122715; Wed, 02 Mar 2022 12:32:02 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1646253122; cv=none; d=google.com; s=arc-20160816; b=fMSdsC8c/96JGtigBrafoNWq1kg746lnzzUI59O2dihCr9unZqEe/OrX8rV1MOhg5B gYZNuMS/CKPzxcOTVwoCfWPE08GPnkstsa9S5Gent30K4Eb8wdEwGMvSJtbuVwRt+QgN 53RpzOc30kb///BEzMHAQ/GVbnpb2mZtEJbuICfMRhZajQV/cp9n2Y1aaHDStfMviTfs 7I4quFboTgLOJEqjABPVTRrd+dpNH2kBe4pPLA7ieb/ehs0mFDPsiGicCuhVQXj2sKrp kiNx1MqePrD1XwwQmqFPuq92QcrBK3xM0+wEXrmhEo+eVYxSYyLtDfQN4yEqunUWavQI NIvw== 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=1v9JSu1lrD0epitW4IwwNrxKFlw6NIclgzuozB1folg=; b=l/uAvRcu7I84ds+/Ai2Z4MPQdJt4Idwp0eE7l8y+3PNwpnmyuZcqmxwncxDchcRFQ3 lyF9QN7O0RwNfPjlPUC2GwxZRM4opiS0byJixde/aM8HW1/wQWvQl6wMrFWLQ0GNHwqe vUUyCkSgsqbN7ls5f2NY7jgzTs1vDmtRAhGn/29xRaAK6ncX5RCg8izSGNZaYkgukOJt 6kU9Hkznl5T59Md0cSFNj/nHEE2M3TrMWF1JunMNhS8va34S+LdkKnej/sl2rZmBncyC 560rz8HgrNB/8oKYAHvwLGZTvc1AETOmtAX5+qUywXpRqZX4nnYo2HrjCzTWXNkGOZLe IDgA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=AoU+nU+Y; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 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 out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id r24-20020a170906549800b006d0ebaf72a9si39747ejo.342.2022.03.02.12.31.39; Wed, 02 Mar 2022 12:32:02 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=AoU+nU+Y; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 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 S241884AbiCBQVD (ORCPT + 99 others); Wed, 2 Mar 2022 11:21:03 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43888 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241849AbiCBQVC (ORCPT ); Wed, 2 Mar 2022 11:21:02 -0500 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 667297D01D; Wed, 2 Mar 2022 08:20:18 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 1C175B81F51; Wed, 2 Mar 2022 16:20:17 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4E8D8C004E1; Wed, 2 Mar 2022 16:20:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1646238015; bh=XNeX32660m2tVj90WpPs9Can/L/FmgVh79u8e7ojpKQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=AoU+nU+YqqvJSnaT8yDbv2jky19r3fSFdyBOTmY/9L7i5GSmg/XiGmnv7e7wWKIPq hZ47SBXIvruM/TqMWGfmOpOENgy+oNLuGgr/Kn7z8+tIQdYaS0ai5CprR11K42mHDN HdEu0/4+zvxOUzWTubQU957FZvRfgpdakNdzpJgo= Date: Wed, 2 Mar 2022 17:20:13 +0100 From: Greg KH To: Steven Rostedt Cc: Jithu Joseph , hdegoede@redhat.com, markgross@kernel.org, tglx@linutronix.de, mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com, corbet@lwn.net, andriy.shevchenko@linux.intel.com, ashok.raj@intel.com, tony.luck@intel.com, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, platform-driver-x86@vger.kernel.org, patches@lists.linux.dev, ravi.v.shankar@intel.com Subject: Re: [RFC 00/10] Introduce In Field Scan driver Message-ID: References: <20220301195457.21152-1-jithu.joseph@intel.com> <20220302103313.3bacd10b@gandalf.local.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220302103313.3bacd10b@gandalf.local.home> X-Spam-Status: No, score=-7.5 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 02, 2022 at 10:33:13AM -0500, Steven Rostedt wrote: > On Tue, 1 Mar 2022 21:10:20 +0100 > Greg KH wrote: > > > "RFC" means you are not comfortable submitting the changes yet, so you > > don't need my review at this point in time. Become confident in your > > changes before asking for others to review the code please. > > I guess you and I have a different understanding of RFC (Request for > Comments). As to me, comments are a form of review. > > In other words, RFC to me means the review is "does this design look like > it will work", and we should be reviewing the design and overview of the > patches. Not the nitty gritty details (like missed error handling, unless > the design will prevent it). Although, you could add those comments in a > review. > > When I post RFCs, it's not that I'm not comfortable submitting the change, > it's because I want to know if what I'm doing makes sense, and I might be > missing something that will make this effort in vain. > > What ever happen to the "Submit early, submit often" mantra? For patches from "experienced" submitters like this, with reviews from other experienced reviewers already (look at the s-o-b chain here), there's no excuse for it to be a RFC unless something is really odd as the experienced reviewers should have already handled the "comments" portion already. Otherwise their review was kind of pointless, right? I'm all for submitting early, but be confident! Also, I have way too many non-RFC patches to review in my queue, so that means any RFC patches fall to the bottom so I like to give people a reason why I'm not reviewing them, like I did here. thanks, greg k-h