Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp1246079ybe; Fri, 13 Sep 2019 13:24:30 -0700 (PDT) X-Google-Smtp-Source: APXvYqzqq1AhNOOrbM100A8fn7c5V1dXFBgHSq8ddKnEqBkroW6f2Is+5GdclZtP9zPy6Be/1MCR X-Received: by 2002:a50:ce53:: with SMTP id k19mr49520133edj.2.1568406270873; Fri, 13 Sep 2019 13:24:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568406270; cv=none; d=google.com; s=arc-20160816; b=wLJ3tn1xkll+xRuAFXPyKmDKsgClQlxxRwxAJ8vUYQraFzLCTh1wTsf0dp4aIxqV7r 90/udotafwb0OHS5/8VLAzvUQoKVrrY8Nyd88Rn66dykYHG0/BKEwnjAVFBCHfgK9b2d zsZw5WKZrS5nURGynFrtBMFQrC1kb5Lz1w+7u9pKmF6v08vi0r9ZLuqEAlHc2sEij60p Y5zs/06kzA2OqNLJwLbbliKqC9vC0Yk0Eke3oAI2UrKE8Z1NPm8dKqAiXoeMZdxDoov+ gzc8Kms0kGhcXxVeth4E7wVsxMA995AAQmtYSfHorQzvtZFKeDam+TdprVw5uP61CpY/ nj0g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=Ct+ssrxIWs9llxQGDML56km76DnuOZ77wHnEVspsAuw=; b=T7ZMvqiu2G7wYpvfLDhqzFmYej8C1mJg7jcvzZqYGii685Yx2Y+Z77CmyuqDc0kZhC ThZwtAhFYzLucXNpbuSWZUPNe+scEzrHpMzfftoSStVHe09PFAj8bgioBqp2PmF3dKzZ chaSeF5A1HX3GFicy4Plqo7YWeO/LBGdSHn5rFbtFE3ZNXLRsV3bI5gCrQXbpLNlsP2j 4R/NzhiAYDVFMZlVOgiKT/OXFFUYPPq9iK5532JSUU9HqslZL0C/Tuptgpwuz/AHnX1S bIajwmxNNxEAkmZnV9/ThbvUvgrZQGM1M3TmJ4JJ+UHSj6a8s/yw+NwgbrEhwgLLL9+4 H8/w== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g7si7138830edn.20.2019.09.13.13.24.06; Fri, 13 Sep 2019 13:24:30 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388614AbfIMThw (ORCPT + 99 others); Fri, 13 Sep 2019 15:37:52 -0400 Received: from bhuna.collabora.co.uk ([46.235.227.227]:59530 "EHLO bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388393AbfIMThv (ORCPT ); Fri, 13 Sep 2019 15:37:51 -0400 Received: from [IPv6:2804:431:c7f4:5bfc:5711:794d:1c68:5ed3] (unknown [IPv6:2804:431:c7f4:5bfc:5711:794d:1c68:5ed3]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: tonyk) by bhuna.collabora.co.uk (Postfix) with ESMTPSA id 00ECF28EF32; Fri, 13 Sep 2019 20:37:47 +0100 (BST) Subject: Re: [PATCH 4/4] coding-style: add explanation about pr_fmt macro To: Joe Perches , linux-block@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Cc: corbet@lwn.net, axboe@kernel.dk, kernel@collabora.com, krisman@collabora.com References: <20190913185746.337429-1-andrealmeid@collabora.com> <20190913185746.337429-5-andrealmeid@collabora.com> <3028cb117886ccc40f160500bd712f005ff6d5f3.camel@perches.com> From: =?UTF-8?Q?Andr=c3=a9_Almeida?= Message-ID: <660cb3cf-1e19-fb0e-9ca6-89f50d5bfd33@collabora.com> Date: Fri, 13 Sep 2019 16:36:42 -0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.0 MIME-Version: 1.0 In-Reply-To: <3028cb117886ccc40f160500bd712f005ff6d5f3.camel@perches.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 9/13/19 4:08 PM, Joe Perches wrote: > On Fri, 2019-09-13 at 15:57 -0300, André Almeida wrote: >> The pr_fmt macro is useful to format log messages printed by pr_XXXX() >> functions. Add text to explain the purpose of it, how to use and an >> example. > [] >> diff --git a/Documentation/process/coding-style.rst b/Documentation/process/coding-style.rst > [] >> @@ -819,7 +819,15 @@ which you should use to make sure messages are matched to the right device >> and driver, and are tagged with the right level: dev_err(), dev_warn(), >> dev_info(), and so forth. For messages that aren't associated with a >> particular device, defines pr_notice(), pr_info(), >> -pr_warn(), pr_err(), etc. >> +pr_warn(), pr_err(), etc. It's possible to format pr_XXX() messages using the >> +macro pr_fmt() to prevent rewriting the style of messages. It should be >> +defined before including ``include/printk.h``, to avoid compiler warning about > > Please make this '#include ' > > printk.h should normally not be #included. > Thanks for the feedback, changed for v2.