Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp6945548imm; Sun, 20 May 2018 14:34:26 -0700 (PDT) X-Google-Smtp-Source: AB8JxZodxKKsxreXdas7yTC2UOHjNLiy+Yv9KX2r9qmp98l5ngfYNTo/ZXdd+MEmNk7vMUTo0KKy X-Received: by 2002:a17:902:9a98:: with SMTP id w24-v6mr5008291plp.9.1526852066402; Sun, 20 May 2018 14:34:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1526852066; cv=none; d=google.com; s=arc-20160816; b=mEULVPuogcXA76us8+icRkix3hZgVcZu63T5lBbbihLW0ivwkX8LybQL8AT6pefo+A Zui7wmnkajJklQO8LuFqBvxLoaYlSS90eN/vGFjLaCd/5I1iacFx8dgwuc9xOWPMhxOu NMbdz0FY/OgddV3CJFIDOMGTL/JM99Q4EXQp544QEqSU7gS4OfupxvODxTcRQa1It8PH NM41MwRCAsomti+JZ5kFS/n/RubffIN0bLCCq00IfY3uVuBH8cS1D/IgE8ChGWPnfrHZ kzA2n2Gay8QSpRmh/AABY6BKsI2j3oFbnL9yMaMRK+bjhwpza8neVBoVFs6j51eBOwg0 xRAw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:arc-authentication-results; bh=sNOCUYXDAZ7winbHaKJgMn6pK3FbvCMWJ+DUlZngcAU=; b=h3ZnvIrw/kzjlWnwbPDayBSRGiB6KFexncCSHSvjA13aexQZr06JWdN/vSgcIOSoUZ vum+7NHK4/wc8VyAFCLYeYtBwmqIOoH+FcwtmFmsSO9bXvdeWVgQzczA/nJ0hAQ83jfg AQ3V+CmyPyNGdEJuhTziJLRCDC2bEWqIDwN4cj+IqG607ILjM6dfJ2xyTZFVhozQVxj1 9RPlXTndBtVfR0SlpcJmuOxxsEQkkJ7QoSFjMIG5sPmxBaRMIJFsT/4X2AzikDw3fLvB MtJcAnNSFAMbx/NjkbzQR8AbvjvxEHCOkp7tWddQmpZ3vRram7TBS4uHOQTUnjLQhH39 zlvg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=H8RFoJQD; 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 d37-v6si12789157plb.125.2018.05.20.14.34.11; Sun, 20 May 2018 14:34:26 -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=H8RFoJQD; 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 S1751685AbeETVd5 (ORCPT + 99 others); Sun, 20 May 2018 17:33:57 -0400 Received: from mail-qk0-f194.google.com ([209.85.220.194]:40410 "EHLO mail-qk0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751067AbeETVdz (ORCPT ); Sun, 20 May 2018 17:33:55 -0400 Received: by mail-qk0-f194.google.com with SMTP id a74-v6so3147634qkg.7; Sun, 20 May 2018 14:33:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=sNOCUYXDAZ7winbHaKJgMn6pK3FbvCMWJ+DUlZngcAU=; b=H8RFoJQDYdAjarY135KAE6TOUm2fjySrgYEwb4JsUkpmtgA10SL5m2VWAb8g4JGhf/ RJ4mSukZXYcZpGJuhRa32oUga5wDh+FwHGNOmbfbinq8TSKdGws+8xi24j0iNmqlpEhs YB4MRw+ZLlsUHbbJD6/931sgx0O8OqC+HS5qEG+PwkfxTgwVDUDm68iyLVGy+D8f5CMa +sQB0jNAWY8RazB9bPQAPSS/9SDKpH1iG5tTE8vMUAuHonwSzEVkeH+c2Vf/wQ+0guvq xyVzFxr+3DEgEp27Llg4IdPJ8Ir+s/8yH6vF0IxssldPoyHdJuUR+8D5D/EEpPypF4vJ Halg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=sNOCUYXDAZ7winbHaKJgMn6pK3FbvCMWJ+DUlZngcAU=; b=qjf3lLCmgU3bo8s3D4mS5jpLQLpjp2cHcB8kYEiBFbH5BDicbygFFf5N0AYd/0wa5/ MyNJHmXCO+BkVs1D2kE/Yu16zYhGD+K62D+9GmZZgoBwJsspydkBc1Um26bCRW5l2FTo exH0ohDIJitPHa4jaO6edtw1RnmtET9u2DayBkCM/pkrbIgf969ZaesHurX5BWLR0E8j yvANMkPPTAn9jJbD/pBnX2dVnEfMbAH6pzT2UlylyyNB1GLJIWay9VgoMg1+RCqYuNAO fpfYyxmJMAXdU1LXExhxkCEiyxXw3iy7pAhr5YuJVBcho9/ZWM+d2GunsXIYwvGBfjD0 pM0Q== X-Gm-Message-State: ALKqPwdhWFvfRNKg1SB2cRYdvIJfc3/Qs3fMDqKyZzqYSTkoj8LdV0oA whvodrtYuiIXCwbDzlzbUR4= X-Received: by 2002:a37:6b82:: with SMTP id g124-v6mr15680433qkc.386.1526852034604; Sun, 20 May 2018 14:33:54 -0700 (PDT) Received: from localhost.localdomain ([45.4.239.227]) by smtp.gmail.com with ESMTPSA id s19-v6sm9635100qki.62.2018.05.20.14.33.52 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 20 May 2018 14:33:53 -0700 (PDT) Received: by localhost.localdomain (Postfix, from userid 1000) id A61E91810B9; Sun, 20 May 2018 18:33:49 -0300 (-03) Date: Sun, 20 May 2018 18:33:49 -0300 From: Marcelo Ricardo Leitner To: Or Gerlitz Cc: Vlad Buslov , Linux Netdev List , David Miller , Jamal Hadi Salim , Cong Wang , Jiri Pirko , Pablo Neira Ayuso , kadlec@blackhole.kfki.hu, Florian Westphal , Alexei Starovoitov , Daniel Borkmann , Eric Dumazet , keescook@chromium.org, Linux Kernel , netfilter-devel@vger.kernel.org, coreteam@netfilter.org, Yevgeny Kliteynik Subject: Re: [PATCH 13/14] net: sched: use unique idr insert function in unlocked actions Message-ID: <20180520213349.GC26212@localhost.localdomain> References: <1526308035-12484-1-git-send-email-vladbu@mellanox.com> <1526308035-12484-14-git-send-email-vladbu@mellanox.com> <20180519222028.GF5488@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, May 21, 2018 at 12:13:06AM +0300, Or Gerlitz wrote: > On Sun, May 20, 2018 at 1:20 AM, Marcelo Ricardo Leitner > wrote: > > On Mon, May 14, 2018 at 05:27:14PM +0300, Vlad Buslov wrote: > >> Substitute calls to action insert function with calls to action insert > >> unique function that warns if insertion overwrites index in idr. > > > > I know this patch may be gone on V2, but a general comment, please use > > the function names themselves instead of a textualized version. I.e., > > s/action insert unique/tcf_idr_insert_unique/ > > disagree. While doing reviews I found out that if I ask the developer > to use higher > level / descriptive language and specifically to avoid putting > variable / function names in > patch titles and change logs, the quality gets ++ big time, vs if the > developer is allowed to say > > net/mlx5: Changed add_vovo_bobo() > > Added variable do_it_right to add_vovo_bobo(), now we are terribly good. In your example I agree that it is not helping and it is even allowing such empty changelog, just as in the section I highlighted, the descriptive language is also not helping IMHO. I had to read it 3 times to make sure I wasn't missing a modifier word when comparing the two functions and well, it's just saying "Substitute calls to foo function to bar function". I don't see how the textualized version helps in this case while, at least in this one, I would have visually recognized the function names way faster. Sounds like 2 bad examples for either approach.