Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp1199064pxb; Fri, 21 Jan 2022 12:04:57 -0800 (PST) X-Google-Smtp-Source: ABdhPJzbFAuioqAOmaE0PQ8ghRMFDPO/8+MFBY2uBhBO8NWLlpCzF6f1ivZFG9eYk3pphiP0plbx X-Received: by 2002:a17:90b:3b46:: with SMTP id ot6mr2276710pjb.104.1642795497213; Fri, 21 Jan 2022 12:04:57 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1642795497; cv=none; d=google.com; s=arc-20160816; b=x4+mVoc9eVtkYh4ecGx8a9d7IxMBQ6Gl37qhQ/NvTx0CxMEvo444SI9NMCnbpmGJXD nTQpBxVXIwldaKNxXGnOuMQgbaDI2T61MAzlmkz2eZ++tgCoR2RCsQsVI43t4S78HfmT rq8mJbv1+NOcKafPdajoOfAf5m5j3duTwGze9QLbExf/GZ0E8rdNtPSBj4F5g/rwHrPf yl6zv1hk0r4kEIYtjqH/hog4WDi6q9oKHkzGetmrPGMH+RHUWxMV6yGfAqxu/JEVlrXL 0Wrw1q1bEiLifm2nj6Xf+BMkq+iq86D8Wv2TuHblUdnyyPRNOE5oJ6mI6qPuR6IZh7bU LrLA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:to:from:date:dkim-signature; bh=esF/8rWtp2QCOw6rc9gKP51Ce7FmpV7I1kyzh4nnsME=; b=k6aGTQEHuFKsbO9TrQWw8aLMKSi2fip1C9f6eCcn93Dg32P0sKQSTxnaCx1F4/FWJq pav8r3vgOd96MDWiWfHlXu8zoq6DOvgw33VYW612Qh2nr0/Db/jVmIvptXp/Ml5rHfRw Rr3OFra9+hXGhKzfLkO+uPxESO+jk5frnS0dFCD7vzXOr25Y+RIsOc7kcIzAi/vsLNwW 7VTo+QjMy3DyI/cV4I7s/kLsZkGgVG+5as6uTUWqOUrMh2fbuw1abTfGzFQvdGSNhJZ5 fEIrevxpilg0CGwjvlu7m1VTX7UBA8apTS34PWB1Ytq1Z3gceGcddR8d7lqwt3wCg8d6 UqHQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=N5V9BrYP; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id mw5si15254116pjb.87.2022.01.21.12.04.45; Fri, 21 Jan 2022 12:04:57 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=N5V9BrYP; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235831AbiASUxs (ORCPT + 99 others); Wed, 19 Jan 2022 15:53:48 -0500 Received: from mga09.intel.com ([134.134.136.24]:55117 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229683AbiASUxq (ORCPT ); Wed, 19 Jan 2022 15:53:46 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1642625626; x=1674161626; h=date:from:to:subject:message-id:references:mime-version: in-reply-to; bh=cH3bHFZpGH0RESw8RskOlsgeHxPQYCpLCLkrUAgJ7oE=; b=N5V9BrYPZPe3+kNXJlVabWxsBtq7kBqY2EhPMRwpa8ZvXa3m07nkcgr/ Q+lHFLsNHXStpIWuiUtZGItH2cEt2JEjDp7IQJTpE1i6EEtbODPef+3FU OV/JI1IKdZzmKbu3U+fFKqWZAM9JILGZwX0/w1JRjA7j/1bceMy3tF8eF EN9/KiqLGG0M5+BKMQoOgiNZCU8eJ6023VC7oUVfoRqWPrmTbq8eH1TPS Op2CrI2jwEiWYjtMNpUz2MJjz0S8HFb3rlTkR0sVfjMqtPe3dQTpWMtyV bbemB1boFVF2qw/ZhBHqoiVlLgZ0CaXQ4zhReCc21iP3I119Ia2wPqalu w==; X-IronPort-AV: E=McAfee;i="6200,9189,10231"; a="244984193" X-IronPort-AV: E=Sophos;i="5.88,300,1635231600"; d="scan'208";a="244984193" Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 19 Jan 2022 12:53:45 -0800 X-IronPort-AV: E=Sophos;i="5.88,300,1635231600"; d="scan'208";a="765081592" Received: from atefehad-mobl1.amr.corp.intel.com (HELO ldmartin-desk2) ([10.212.238.132]) by fmsmga006-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 19 Jan 2022 12:53:44 -0800 Date: Wed, 19 Jan 2022 12:53:43 -0800 From: Lucas De Marchi To: Jani Nikula , Petr Mladek , linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org, linux-security-module@vger.kernel.org, nouveau@lists.freedesktop.org, netdev@vger.kernel.org, Alex Deucher , Andrew Morton , Andy Shevchenko , Andy Shevchenko , Ben Skeggs , Christian =?utf-8?B?S8O2bmln?= , Chris Wilson , David Airlie , "David S . Miller" , Emma Anholt , Eryk Brol , Francis Laniel , Greg Kroah-Hartman , Harry Wentland , Jakub Kicinski , Joonas Lahtinen , Julia Lawall , Kentaro Takeda , Leo Li , Mikita Lipski , Rahul Lakkireddy , Raju Rangoju , Rasmus Villemoes , Rodrigo Vivi , Sakari Ailus , Sergey Senozhatsky , Steven Rostedt , Vishal Kulkarni Subject: Re: [Intel-gfx] [PATCH 0/3] lib/string_helpers: Add a few string helpers Message-ID: <20220119205343.kd5cwfzpg4mlsekk@ldmartin-desk2> X-Patchwork-Hint: comment References: <20220119072450.2890107-1-lucas.demarchi@intel.com> <87tudzbykz.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 19, 2022 at 05:15:02PM +0100, Daniel Vetter wrote: >On Wed, Jan 19, 2022 at 04:16:12PM +0200, Jani Nikula wrote: >> On Wed, 19 Jan 2022, Petr Mladek wrote: >> > On Tue 2022-01-18 23:24:47, Lucas De Marchi wrote: >> >> Add some helpers under lib/string_helpers.h so they can be used >> >> throughout the kernel. When I started doing this there were 2 other >> >> previous attempts I know of, not counting the iterations each of them >> >> had: >> >> >> >> 1) https://lore.kernel.org/all/20191023131308.9420-1-jani.nikula@intel.com/ >> >> 2) https://lore.kernel.org/all/20210215142137.64476-1-andriy.shevchenko@linux.intel.com/#t >> >> >> >> Going through the comments I tried to find some common ground and >> >> justification for what is in here, addressing some of the concerns >> >> raised. >> >> >> >> d. This doesn't bring onoff() helper as there are some places in the >> >> kernel with onoff as variable - another name is probably needed for >> >> this function in order not to shadow the variable, or those variables >> >> could be renamed. Or if people wanting >> >> try to find a short one >> > >> > I would call it str_on_off(). >> > >> > And I would actually suggest to use the same style also for >> > the other helpers. >> > >> > The "str_" prefix would make it clear that it is something with >> > string. There are other _on_off() that affect some >> > functionality, e.g. mute_led_on_off(), e1000_vlan_filter_on_off(). >> > >> > The dash '_' would significantly help to parse the name. yesno() and >> > onoff() are nicely short and kind of acceptable. But "enabledisable()" >> > is a puzzle. >> > >> > IMHO, str_yes_no(), str_on_off(), str_enable_disable() are a good >> > compromise. >> > >> > The main motivation should be code readability. You write the >> > code once. But many people will read it many times. Open coding >> > is sometimes better than misleading macro names. >> > >> > That said, I do not want to block this patchset. If others like >> > it... ;-) >> >> I don't mind the names either way. Adding the prefix and dashes is >> helpful in that it's possible to add the functions first and convert >> users at leisure, though with a bunch of churn, while using names that >> collide with existing ones requires the changes to happen in one go. >> >> What I do mind is grinding this series to a halt once again. I sent a >> handful of versions of this three years ago, with inconclusive >> bikeshedding back and forth, eventually threw my hands up in disgust, >> and walked away. > >Yeah we can sed this anytime later we want to, but we need to get the foot >in the door. There's also a pile more of these all over. > >Acked-by: Daniel Vetter > >on the series, maybe it helps? And yes let's merge this through drm-misc. Ok, it seems we are reaching some agreement here then: - Change it to use str_ prefix - Wait -rc1 to avoid conflict - Merge through drm-misc I will re-send the series again soon. Lucas De Marchi