Received: by 2002:a05:6358:f14:b0:e5:3b68:ec04 with SMTP id b20csp5915305rwj; Wed, 21 Dec 2022 08:31:49 -0800 (PST) X-Google-Smtp-Source: AMrXdXton7kLdLxzZt4dbv5VFfQV5hrod5KktqGqk7fE++Ix7fyAs+vgwyLyFyCRSzstXB8shsA0 X-Received: by 2002:a17:907:c28f:b0:7c1:eb:b2a7 with SMTP id tk15-20020a170907c28f00b007c100ebb2a7mr5905888ejc.13.1671640308985; Wed, 21 Dec 2022 08:31:48 -0800 (PST) ARC-Seal: i=2; a=rsa-sha256; t=1671640308; cv=pass; d=google.com; s=arc-20160816; b=lqELmMWNLRQY7KRRBSeo3ab+U2ehK7m2PdgU8886mgDnAizbyGcokGhugkf6Ov8rBp 4/Wm1LtyCM1HHc4fEfLMiXyUr/+EcGdo4bmp2/5iRBKMI7UvhsXY8KdmMzvah/YrFsaS vw2KcOJer4jt/+eplEh+KmqPm2LtcjLBzy3dA05Ksp0VaMZv5j5juyLkXPomStMFq5W5 JLHFagQ+qb81vaAuEjWglU86KLx5Kj3U2Ne9P0lJ4dMe9is7EZj9SC1IcUAn0GVosn0/ nQ/MzZZzZoK0pF4NDVFTHrkFB9tTiXcaMDGoo1JlCh6YnmsqoDHw3hZFMZpQBZ7Vlajv pD2g== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=Of6vrR1lUd/EV67jSnxQeaQIY4MOTKhA+LjhfYeG4/0=; b=b181narDjVs72MDdvc7IXEmsj3KRlx7zYx0UhATfVn/WDsB24JOVn+AmFWB8gP/wFS +10nhqh764JvYA7SgTMZIma5REfY13+3U3td7sujzlsN5ZueRrj38TptlNbkDMeKAeby 8OT0xifaVQGpeBGLrnNKd0ZOuHmPxr/g5PLy3MVo72J9rgXOiRCopDXDCywUiR/mpCqW +Id96eWeujWsYtVCzuu9K+uHGS+OmFYIIZbAhgkN+uNtFUMwUD4EZosHqJbyJdFS/sd/ 3mgoTUbx24T3yPKqnn9zEBJ4beQWASEJLviLLTGWdLJx62u7m8F5Io7i0vtqM+MrMVgN S69Q== ARC-Authentication-Results: i=2; mx.google.com; dkim=pass header.i=@siddh.me header.s=zmail header.b=oaRwvIHB; arc=pass (i=1 spf=pass spfdomain=siddh.me dkim=pass dkdomain=siddh.me dmarc=pass fromdomain=siddh.me>); 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=REJECT sp=REJECT dis=NONE) header.from=siddh.me Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id du19-20020a17090772d300b007986956bd8esi4181393ejc.472.2022.12.21.08.31.33; Wed, 21 Dec 2022 08:31:48 -0800 (PST) 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=@siddh.me header.s=zmail header.b=oaRwvIHB; arc=pass (i=1 spf=pass spfdomain=siddh.me dkim=pass dkdomain=siddh.me dmarc=pass fromdomain=siddh.me>); 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=REJECT sp=REJECT dis=NONE) header.from=siddh.me Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230330AbiLUP62 (ORCPT + 68 others); Wed, 21 Dec 2022 10:58:28 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48902 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229981AbiLUP60 (ORCPT ); Wed, 21 Dec 2022 10:58:26 -0500 Received: from sender-of-o50.zoho.in (sender-of-o50.zoho.in [103.117.158.50]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9649413D4F for ; Wed, 21 Dec 2022 07:58:24 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1671638279; cv=none; d=zohomail.in; s=zohoarc; b=R4M5zinm++np+BA4HudMlH3uOWC0Mn1BnGE0uXGjJ1MREO6sgz+G3EdZvj13nVOUQ/rMR4fb8gPe/spJaoz4MDixGCw6yn1ir0r8iVSDlLleKBR58fs4OYZgnz3d0BQtU9ri90RGJfusGb+2ShvaGOneDef5ZnYU+A2f0uncZt0= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.in; s=zohoarc; t=1671638279; h=Content-Type:Content-Transfer-Encoding:Cc:Date:From:In-Reply-To:MIME-Version:Message-ID:References:Subject:To; bh=Of6vrR1lUd/EV67jSnxQeaQIY4MOTKhA+LjhfYeG4/0=; b=TD6hAwMy8mgMDMS5vGQtPqAeZQrwoWM/2VDAivAHPZshz/RgmcXwBEIZg4KuwVF6qXTMsGKp4ELNi9w7hVPe7rN/bJB2/k2y8iePHERaePq+SnZH6z/Ff3C821OHHcFzBtfX9gWPk8SZzcUJYJAwoN6SwuWvSl46WHuQ7tQa8Ys= ARC-Authentication-Results: i=1; mx.zohomail.in; dkim=pass header.i=siddh.me; spf=pass smtp.mailfrom=code@siddh.me; dmarc=pass header.from= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1671638279; s=zmail; d=siddh.me; i=code@siddh.me; h=Message-ID:Date:Date:MIME-Version:Subject:Subject:To:To:Cc:Cc:References:From:From:In-Reply-To:Content-Type:Content-Transfer-Encoding:Message-Id:Reply-To; bh=Of6vrR1lUd/EV67jSnxQeaQIY4MOTKhA+LjhfYeG4/0=; b=oaRwvIHBMd8+sh8uRX1DWmJjMiTivq/CzkDAIb6qQWjc34F1Z2D5zVHdlUwvZRb/ Wkf6XT+y0nmYbGa7g57viGT2t+vnuVF33dlnv1qPucvypxSrcuOcqmeKQXRFJQmU6lE 2pF2g0WRyks0uRIMxm+21JqV3Xn6mUp9ckzC+2W0= Received: from [192.168.1.9] (110.226.31.37 [110.226.31.37]) by mx.zoho.in with SMTPS id 1671638277556109.11418111263356; Wed, 21 Dec 2022 21:27:57 +0530 (IST) Message-ID: <251def1c-5577-6b7b-4ebe-4a1feb4687af@siddh.me> Date: Wed, 21 Dec 2022 21:27:56 +0530 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.1 Subject: Re: [PATCH 00/10] drm: Remove usage of deprecated DRM_* macros Content-Language: en-US, en-GB, hi-IN To: Thomas Zimmermann , Jani Nikula Cc: dri-devel , linux-kernel , Maarten Lankhorst , Maxime Ripard , David Airlie , Daniel Vetter References: <339505f3-9005-df0b-3c73-b54320568db2@suse.de> From: Siddh Raman Pant In-Reply-To: <339505f3-9005-df0b-3c73-b54320568db2@suse.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-ZohoMailClient: External X-Spam-Status: No, score=-3.2 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_NONE, 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 Wed, Dec 21 2022 at 14:46:12 +0530, Thomas Zimmermann wrote: > Hi > > Am 20.12.22 um 21:16 schrieb Siddh Raman Pant: >> This patchset aims to remove usages of deprecated DRM_* macros from the >> files residing in drivers/gpu/drm root. >> >> In process, I found out that NULL as first argument of drm_dbg_* wasn't >> working, but it was listed as the alternative in deprecation comment, >> so I fixed that before removing usages of DRM_DEBUG_* macros. >> >> This patchset should be applied in order as changes might be dependent. >> >> Please review and let me know if any errors are there, and hopefully >> this gets accepted. > > Thanks for the patchset. Overall this looks fine. > > But the use of pr_() functions is not optimal in my opinion. I know that > I recommended using it, but at a closer look, I think we might want to > reconsider that. I wouldn't like losing the '[drm]' tag, but adding them > to each pr_() call isn't a good idea either. > > I think it would be nicer to replace DRM_INFO with drm_info(NULL, ). > Depending on the device being NULL, the helpers would select dev-based > messages or printk-based messages. It would then work like drm_dbg_(). > But it needs some additional changes. > > Can you first move all pr_() related changes into a new patchset? The > trivial conversion were the device is known and not NULL can remain in > this patchset and be merged soon. We can afterwards have a separate > discussion for the changes that currently involve pr_(). > > Best regards > Thomas Maybe I can just cope for NULL in __drm_printk and change all pr_*() changes in this patchset to the appropriate ones. Something like: #define __drm_printk(drm, level, type, fmt, ...) \ ({ \ drm_ = __drm_print_dev(drm); \ if (drm_) \ dev_##level##type((drm_)->dev, "[drm] " fmt, ##__VA_ARGS__); \ else \ pr_##level##type("[drm] " fmt, ##__VA_ARGS__); \ }) Thanks, Siddh