Received: by 2002:a05:6358:1087:b0:cb:c9d3:cd90 with SMTP id j7csp232922rwi; Fri, 14 Oct 2022 00:49:53 -0700 (PDT) X-Google-Smtp-Source: AMsMyM7odmRkyR8RMh56unE9cPBE5F51njXZSnEdHDiEC63XaZ4H9aOn+SOXkgEdsPP5m0U8z34P X-Received: by 2002:aa7:d744:0:b0:45c:e353:e891 with SMTP id a4-20020aa7d744000000b0045ce353e891mr3271253eds.36.1665733792934; Fri, 14 Oct 2022 00:49:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1665733792; cv=none; d=google.com; s=arc-20160816; b=uiU0d7frBB1O9/uVeMWBQ8vqSr/qrSyj34VY6ag9joeEwuT9ym6xDnp1KCIXZZv64b H4IkeaTnlzhGSrEZ3bklfftAPuU3A8u+I8m6mhV+TMVMTaF814LF/DfYjfnoMRzR+Sr7 Ng2cOT3eoWQSD1WRLPz0FPauaVETjTCp2SRNmUR3IycXxY2ZmQ0BV3V/eKQB/XrxN9L6 x7RaNoeyJzD5XPaPUO9QgcfZUPKJMMPjxds6ZKVj2r3LcmRXsB/lx7DRPUGvwaM6G14o aUrxyS81lu7wWcgFbDloi2C+ZjojA6mCixn85eLsDkoGu8gU3MSDq5FrPbRkkR7RoxQ3 Dkvw== 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=PBhae3ZCZ+fNcGyConJppgLccycmqb4USPXiKpDYLI0=; b=wLTItthWo2SrR67jFh+/maffQa9WvWMPcY4QUo25cInPrZpGv+yNbJinT6DkNOCKLO 0D6loe0OJYGlZCf3Hl/SdbOJlkZCGMSphHEnKV15t/ucvwuDRDIuqO+4972o2rfBHKm/ 72jfYrPPCGUd4iNByCyplwJ5Xr2iHQdY52/g6ksvDV2zwZhNSTms4tvmCZboVl1qRKQ2 gvUPpSos5LFAt7/OM8g4ct21Xoc/+eFBGI/uGnwfcVyvdiLlZMQYJV1ScxCqBqh7Kd+Z IZBQdZcYoaiCM8RsrNFp+J6uQmrn0K7U3Fyd81s57fh4ZbYrXTHUPiaYlgiS8IsF1C07 HAEA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=U+A8gMjd; 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 nb36-20020a1709071ca400b0078ddffd4660si1963759ejc.651.2022.10.14.00.49.27; Fri, 14 Oct 2022 00:49:52 -0700 (PDT) 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=U+A8gMjd; 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 S229436AbiJNHOr (ORCPT + 99 others); Fri, 14 Oct 2022 03:14:47 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53646 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229555AbiJNHOm (ORCPT ); Fri, 14 Oct 2022 03:14:42 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7D45A2C5; Fri, 14 Oct 2022 00:14:36 -0700 (PDT) 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 dfw.source.kernel.org (Postfix) with ESMTPS id 0217561A21; Fri, 14 Oct 2022 07:14:36 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id D3B46C433D6; Fri, 14 Oct 2022 07:14:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1665731675; bh=XIkzcs9sFTLKy2SGQR+FJTYqZbqKMl+CzpRoO0bQ9Zw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=U+A8gMjdJuFM5PwXc4qk1fUqpOqtIugtD1kt1TTLaBrcI+J5wF3m/QGdf9LQEYVCX bjcedEscToBui6t/AaPjWgnD6lkzLU4SXPHe2veQIkBqcPk/2SKobB8AG5B2SK+pvm tnZUGb8LuoyWfSZ9twee2iifM5xZF0ov9EoFZa0Y= Date: Fri, 14 Oct 2022 09:15:20 +0200 From: Greg KH To: Nipun Gupta Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, rafael@kernel.org, eric.auger@redhat.com, alex.williamson@redhat.com, cohuck@redhat.com, puneet.gupta@amd.com, song.bao.hua@hisilicon.com, mchehab+huawei@kernel.org, maz@kernel.org, f.fainelli@gmail.com, jeffrey.l.hugo@gmail.com, saravanak@google.com, Michael.Srba@seznam.cz, mani@kernel.org, yishaih@nvidia.com, jgg@ziepe.ca, jgg@nvidia.com, robin.murphy@arm.com, will@kernel.org, joro@8bytes.org, masahiroy@kernel.org, ndesaulniers@google.com, linux-arm-kernel@lists.infradead.org, linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, kvm@vger.kernel.org, okaya@kernel.org, harpreet.anand@amd.com, nikhil.agarwal@amd.com, michal.simek@amd.com, aleksandar.radovanovic@amd.com, git@amd.com Subject: Re: [RFC PATCH v4 2/8] bus/cdx: add the cdx bus driver Message-ID: References: <20220803122655.100254-1-nipun.gupta@amd.com> <20221014044049.2557085-1-nipun.gupta@amd.com> <20221014044049.2557085-3-nipun.gupta@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20221014044049.2557085-3-nipun.gupta@amd.com> X-Spam-Status: No, score=-7.1 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 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 Fri, Oct 14, 2022 at 10:10:43AM +0530, Nipun Gupta wrote: > CDX bus supports the scanning and probing of FPGA based > devices. These devices are registered as CDX devices. > > The bus driver sets up the basic infrastructure and triggers > the cdx controller to scan the cdx devices once registered. > > CDX bus uses ops registered by the CDX controller to scan, > reset and write MSI message on the CDX devices. > > Signed-off-by: Nipun Gupta Why is this all still "RFC"? RFC means to me, "I don't know what to do here, so here's a half-baked proposal". When you are on v4 of a RFC, that is a huge sign that this all isn't working at all. Also, where is the questions that you still have that you need help with here? Also, I don't review RFC changes normally as that means the submitter doesn't think they are good enough to be submitted, so why would I review them when I have hundreds of other changes that submitters do think are good enough? Can you just submit these "for real" if they work properly for you and you have tested them and you would be happy if they are accepted. thanks, greg k-h