From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3CF33C2D0E4 for ; Sun, 15 Nov 2020 06:49:16 +0000 (UTC) Received: from alsa0.perex.cz (alsa0.perex.cz [77.48.224.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 4693D2240B for ; Sun, 15 Nov 2020 06:49:13 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alsa-project.org header.i=@alsa-project.org header.b="io0VbGIF" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 4693D2240B Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=nvidia.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=alsa-devel-bounces@alsa-project.org Received: from alsa1.perex.cz (alsa1.perex.cz [207.180.221.201]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id E34491852; Sun, 15 Nov 2020 07:48:21 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz E34491852 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1605422952; bh=vp8Vrti7ru30WjpTviHFxFT+GLuIXKEIdOWeS+G6+CE=; h=Date:From:To:Subject:References:In-Reply-To:Cc:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=io0VbGIFsRbAkpJ/2Qs6j5XeIE3sLHsTrY9vxh59nfVVvDpnsxgZU69ad4vopFOiw d3hhDDZzj9hH1YLbKzYbaBhRU1G2bimnaf9b9ZeybxVo/Lar0wJz6hdlTw77Dqh5rq BQ3Zm04VmkcckT5U5cTEztDjwJ1jDH8w7/5RgylE= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id 501E7F800E9; Sun, 15 Nov 2020 07:48:21 +0100 (CET) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 5E9A2F801F5; Sun, 15 Nov 2020 07:48:19 +0100 (CET) Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id 420BAF800E9 for ; Sun, 15 Nov 2020 07:48:11 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz 420BAF800E9 Received: from localhost (thunderhill.nvidia.com [216.228.112.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id DA760223AB; Sun, 15 Nov 2020 06:48:05 +0000 (UTC) Date: Sun, 15 Nov 2020 08:48:02 +0200 From: Leon Romanovsky To: Greg KH Subject: Re: [PATCH v3 01/10] Add auxiliary bus support Message-ID: <20201115064802.GB5552@unreal> References: <20201023003338.1285642-1-david.m.ertman@intel.com> <20201023003338.1285642-2-david.m.ertman@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: "alsa-devel@alsa-project.org" , "parav@mellanox.com" , "tiwai@suse.de" , "netdev@vger.kernel.org" , "ranjani.sridharan@linux.intel.com" , "pierre-louis.bossart@linux.intel.com" , "fred.oh@linux.intel.com" , "linux-rdma@vger.kernel.org" , "dledford@redhat.com" , "broonie@kernel.org" , "jgg@nvidia.com" , "kuba@kernel.org" , "Ertman, David M" , "Williams, Dan J" , "Saleem, Shiraz" , "davem@davemloft.net" , "linux-kernel@vger.kernel.org" , "Patil, Kiran" X-BeenThere: alsa-devel@alsa-project.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Alsa-devel mailing list for ALSA developers - http://www.alsa-project.org" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" On Sat, Nov 14, 2020 at 12:21:39AM +0100, Greg KH wrote: > On Fri, Nov 13, 2020 at 04:07:57PM +0000, Ertman, David M wrote: > > > -----Original Message----- > > > From: Greg KH > > > Sent: Friday, November 13, 2020 7:50 AM > > > To: Ertman, David M > > > Cc: alsa-devel@alsa-project.org; tiwai@suse.de; broonie@kernel.org; linux- > > > rdma@vger.kernel.org; jgg@nvidia.com; dledford@redhat.com; > > > netdev@vger.kernel.org; davem@davemloft.net; kuba@kernel.org; > > > ranjani.sridharan@linux.intel.com; pierre-louis.bossart@linux.intel.com; > > > fred.oh@linux.intel.com; parav@mellanox.com; Saleem, Shiraz > > > ; Williams, Dan J ; > > > Patil, Kiran ; linux-kernel@vger.kernel.org; > > > leonro@nvidia.com > > > Subject: Re: [PATCH v3 01/10] Add auxiliary bus support > > > > > > On Thu, Oct 22, 2020 at 05:33:29PM -0700, Dave Ertman wrote: > > > > Add support for the Auxiliary Bus, auxiliary_device and auxiliary_driver. > > > > It enables drivers to create an auxiliary_device and bind an > > > > auxiliary_driver to it. > > > > > > > > The bus supports probe/remove shutdown and suspend/resume callbacks. > > > > Each auxiliary_device has a unique string based id; driver binds to > > > > an auxiliary_device based on this id through the bus. > > > > > > > > Co-developed-by: Kiran Patil > > > > Signed-off-by: Kiran Patil > > > > Co-developed-by: Ranjani Sridharan > > > > Signed-off-by: Ranjani Sridharan > > > > Co-developed-by: Fred Oh > > > > Signed-off-by: Fred Oh > > > > Co-developed-by: Leon Romanovsky > > > > Signed-off-by: Leon Romanovsky > > > > Reviewed-by: Pierre-Louis Bossart > > > > Reviewed-by: Shiraz Saleem > > > > Reviewed-by: Parav Pandit > > > > Reviewed-by: Dan Williams > > > > Signed-off-by: Dave Ertman > > > > --- > > > > > > Is this really the "latest" version of this patch submission? > > > > > > I see a number of comments on it already, have you sent out a newer one, > > > or is this the same one that the mlx5 driver conversion was done on top > > > of? > > > > > > thanks, > > > > > > greg k-h > > > > V3 is the latest sent so far. There was a suggestion that v3 might be merged and > > the documentation changes could be in a follow up patch. I have those changes done > > and ready though, so no reason not to merge them in and do a resend. > > > > Please expect v4 in just a little while. > > Thank you, follow-up patches aren't usually a good idea :) The changes were in documentation area that will be changed anyway after dust will settle and we all see real users and more or less stable in-kernel API. Thanks