Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp1244555ybl; Wed, 28 Aug 2019 11:41:46 -0700 (PDT) X-Google-Smtp-Source: APXvYqxCSabupDlXGh73VASQYf/xPnPfkFzo9qiD0HeOKfdhkPMN5Rxco2fEO1TVsAVmQctn+9V7 X-Received: by 2002:aa7:8c4c:: with SMTP id e12mr6446581pfd.258.1567017706135; Wed, 28 Aug 2019 11:41:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567017706; cv=none; d=google.com; s=arc-20160816; b=u3RnN3TphZylRgdg8rpcnwYDiNjOA2VaUSirRblVK9oM1mz3YLPfNYonPV0UZ8B4s/ 3uzP8zyx8XNa1nXe2I520gvajQlnJ6msK+1g4zCg1IPo3wr+1TpZlVvUSZCroMEloJjL JGs0cwE9nigeDizb9GEyTeTGHxIzCcwl8WXTLRgEpxpeQ8Prg07vXUdQfqDAHtl/kE0j fZVx0qKw3GS7MlnLGSlMW1wbhPbkCDY68opdgpVb5fn3ZXpF3BUkzv9o87b7AD7cSFO3 7bZM49pArqu67iSKMbyCD9Gu4pvSl03Q5R4cZjJdXYP4wDtfdGGmz/JYcrDAzgKFa/GM i0RQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:references:in-reply-to :message-id:cc:to:subject:from:date:dkim-signature; bh=1ZQ5ojymViBrAruzvPsWbm4OehLwZlcgiZDLWBOPkfM=; b=z9qnP418NPTcrroUVus4IfSn6qgCHio9iNi1Wnm6TjAZCems8QEw7Czk2kckKCmOAy /nI+3Wf3N5c4I0bPwCvzkoyDGNLXRgHyYLGotpypY2NMA/lh5SZjcf4ZaJ1SQ8KevxnK D4cdrAz6kon88qHW64zOAs02ssUgXBxx0xC6d8p5f1iZs2Rnx+uanGijB1B3q3CXggin 7cl4lYB6h8as73j49X1LHV/LZJ6TsU4ZqI1BWqmGbMX7zXpch6EfvqSmYZn9VZHDoYWp yJfDVkAj0HaDsF9j4+UP1qIO1D1GKqB951gKP7T/rrdQz2z/J9q9VJEenxvCnpxWtBzv +rFQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=NAU7esjH; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i1si2677829pgs.132.2019.08.28.11.41.29; Wed, 28 Aug 2019 11:41:46 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=NAU7esjH; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726735AbfH1Skd (ORCPT + 99 others); Wed, 28 Aug 2019 14:40:33 -0400 Received: from mail-wm1-f68.google.com ([209.85.128.68]:36725 "EHLO mail-wm1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726515AbfH1Skd (ORCPT ); Wed, 28 Aug 2019 14:40:33 -0400 Received: by mail-wm1-f68.google.com with SMTP id p13so1141501wmh.1; Wed, 28 Aug 2019 11:40:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:subject:to:cc:message-id:in-reply-to:references :mime-version; bh=1ZQ5ojymViBrAruzvPsWbm4OehLwZlcgiZDLWBOPkfM=; b=NAU7esjH2NV9GhK0Lz2BHZ+3nHLUsrrpH5KEinI+cgBB6OOMDv+05mIDKSszvqUnL9 VLyAkrMRInSdFJB6Xm3A6w1yl5FVtiswgPmYF6wIiyyigxfXAutOEd4m+4aC2w/hhAeK 9M8F0uvPPPZaN7rgrCqf5bjoVecefE5kUZQRtL4yXS8N2xh8OYfZvDsUQoGSlIL5c7+u 6NiE2eNs/qDsRCXUEy/ol0ucYicIu0c+Ng7j7/4c1WH8OtBQEgI38sv2AJ6iow7k8mU/ WBTit9nROwHCS6pN6Lfrf3f/qPf5n9pJ7onNZQ8FaDfJJr/XonrmcKtuOAi3b/QZrcM2 xevg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:subject:to:cc:message-id:in-reply-to :references:mime-version; bh=1ZQ5ojymViBrAruzvPsWbm4OehLwZlcgiZDLWBOPkfM=; b=oxEBdhnpZFcCSLsQfamBuUfJ3RsLCLT+95hwGqJwzbYltMZkfyJFNPs7QVqs6jds10 m7pXLDEzLyC3Mv6vxFKbytkPMqEKA7dbxkZeedDq7+ppr5/ZuMOmyzRlugaJqhf0Ten/ mNGNLEU7ZP7+x/kbyc3qil4mM5XDuQ2+JrabSYGjtrAkXSic4xysOURb/d620FjCr63V vHKc0xGZLgCydbRSuZgcybx7FEVilnYh9nQhMkHRwBCNU6PPxcXj4/Ctszhs6JZKA9T+ 4SMyLRotGRRcqSUqwYuDoJH+JMUg3GsgF4l23qams1jBfpAA6lgoQ6QNMJP6+x2fldcT Vqqg== X-Gm-Message-State: APjAAAUCD15ug2ShjTJLnWsGxKN1mH+90cZt45xEHRA2Adt8jjkuCTtT x3i/xnvIWPG28BdoX+sNtzQ= X-Received: by 2002:a05:600c:24cf:: with SMTP id 15mr6641221wmu.76.1567017630452; Wed, 28 Aug 2019 11:40:30 -0700 (PDT) Received: from [192.168.1.105] (ip5b4096c3.dynamic.kabel-deutschland.de. [91.64.150.195]) by smtp.gmail.com with ESMTPSA id n8sm319052wma.7.2019.08.28.11.40.28 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 28 Aug 2019 11:40:29 -0700 (PDT) Date: Wed, 28 Aug 2019 20:40:27 +0200 From: Krzysztof Wilczynski Subject: Re: [PATCH v2] x86/PCI: Add missing log facility and move to use pr_ macros in pcbios.c To: Joe Perches Cc: Krzysztof Wilczynski , Bjorn Helgaas , Thomas Gleixner , Ingo Molnar , Borislav Petkov , "H. Peter Anvin" , x86@kernel.org, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org Message-Id: <1567017627.3507.0@gmail.com> In-Reply-To: References: <20190825182557.23260-1-kw@linux.com> <20190828175120.22164-1-kw@linux.com> X-Mailer: geary/3.32.0 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello Joe, Thank you for feedback. [...] >> Move to pr_debug() over using DBG() from >> arch/x86/include/asm/pci_x86.h. > > You might also consider the checkpatch output for this patch. > > arch/x86/pci/pcbios.c:116: WARNING: line over 80 characters > arch/x86/pci/pcbios.c:116: WARNING: Prefer using '"%s...", __func__' > to using 'bios32_service', this function's name, in a string > arch/x86/pci/pcbios.c:119: WARNING: Prefer using '"%s...", __func__' > to using 'bios32_service', this function's name, in a string > arch/x86/pci/pcbios.c:391: WARNING: line over 80 characters Good point. The lines over 80 characters wide would be taken care of when moving to using the pr_ macros as the line length will now be shorter contrary to when the e.g., printk(KERNEL_INFO ...), etc., was used. The other warnings I am going to address in v3. I was thinking of replacing the following: pr_warn("bios32_service(0x%lx): not present\n", service); With something that looks like this: pr_warn("BIOS32 Service(0x%lx): not present\n", service); Using "bios32_service" name directly or even moving to __func__ feels a lot like an implementation detail is exposed to the end user. I am not sure how useful that could be. Also, we are already using log lines starting with "BIOS32", thus it seemed like following them would be the most sensible choice, especially to keep messages consistent. What do you think? Krzysztof