Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp363975iog; Wed, 15 Jun 2022 03:59:11 -0700 (PDT) X-Google-Smtp-Source: AGRyM1sRcGS7ilpTGNqGAIJv7/B624HpFtxY1XwjM0nUNp6Itc+z6QzWPeFIxsNjE7K/aulr1mox X-Received: by 2002:a17:90b:3904:b0:1ea:d976:aff7 with SMTP id ob4-20020a17090b390400b001ead976aff7mr1986613pjb.4.1655290751542; Wed, 15 Jun 2022 03:59:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1655290751; cv=none; d=google.com; s=arc-20160816; b=kBwkqAdVhVTTRz4xgZ8q3pRhAZT//rPwpM99E8WOcyswAOoGlNyiX8TWW1Aw2IO3jT 3Z86SckflUfC5mFZYoM9vuBOFuFtLJ1AMmcXzU55hvoLuj/xLQnPD5FZQ32cYW+TkUq6 Z/71/F9/VxxozHp5RuGyXmbJ9BWeSwkH3D8eR4XM2xFIb8FMTNXrRV4psvna3/EfNOXQ INJmpdDxtNgdxPMIICyDZxE8/At1mgD2Onfo7qUxEw0fh34WRoXdYjhlYElV0pUsCXtf GTD7VlX9vxaSExZjUUN5jdhGyDshIVOoS/Yqw01+YWoxjcIUWNEAmLkWx/R+cKxDRQEB Oouw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=16flwnJOLHk2cA9kmZHVVcS9bSnf9tyI8d8bncmaE+0=; b=W3Y8V0/dQbJXBGGSEO4anEhj1NbZSdmPnbTg82/u0hSAepSjf7ZBGlFu0X2crPter7 zACbKhJuBcJGwowk2RejjlRpcVsAcnDuu48OCUmNLzF/ADxthx30Y04lWfr6w5Gc9jMi mrfiLSbZuv6W/GA9BI2+uAc75AS0znc4AO8Uoe6OWOqi+N3esxoilp24/gsFzJE74OM8 8t+qCKv86ZywSnbax3P7GiC16MGsvv3Z+PoGMbNplolcdSrIWzAqMC8Td2gGZNwd79nU j3EsvbJWwDDCsIVMps8kWNQB86WSWMLNsmRsR6GPwAU4yDEOclBjuy+Xw5y8utCnLxV/ PAng== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id ls2-20020a17090b350200b001e893b0bd67si2531110pjb.182.2022.06.15.03.58.58; Wed, 15 Jun 2022 03:59:11 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1347318AbiFOKxh (ORCPT + 99 others); Wed, 15 Jun 2022 06:53:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46860 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S243714AbiFOKx0 (ORCPT ); Wed, 15 Jun 2022 06:53:26 -0400 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 13EDD50B25 for ; Wed, 15 Jun 2022 03:53:22 -0700 (PDT) Received: by verein.lst.de (Postfix, from userid 2407) id 2919A68AA6; Wed, 15 Jun 2022 12:53:17 +0200 (CEST) Date: Wed, 15 Jun 2022 12:53:16 +0200 From: Christoph Hellwig To: Erwan Velu Cc: Christoph Hellwig , Keith Busch , Erwan Velu , Jens Axboe , Sagi Grimberg , "open list:NVM EXPRESS DRIVER" , open list Subject: Re: [PATCH 2/2] nvme: Report model,sn,fw,pci device information during init Message-ID: <20220615105316.GA7911@lst.de> References: <20220614210902.744318-1-e.velu@criteo.com> <20220614210902.744318-2-e.velu@criteo.com> <20220615053729.GA21858@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_NONE,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, Jun 15, 2022 at 09:57:05AM +0200, Erwan Velu wrote: > > I would much prefer to not print it all. The Linux boot is way to spammy > > to start with and this doesn't add any real value. > > > > I know the boot is a bit spammy but when systems crash because of nvme > drives, that's very handy to get a trace showing who was the culprit and > what drive is installed (including the fw version which is usually a major > source of troubles). Well, usually they are all the same or a very small set of different SKUs compared to the total number of drives.