linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hongbo Li <lihongbo22@huawei.com>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
	Andy Shevchenko <andy@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>
Cc: <kees@kernel.org>, <jasowang@redhat.com>, <davem@davemloft.net>,
	<edumazet@google.com>, <pabeni@redhat.com>,
	<akpm@linux-foundation.org>, <linux-hardening@vger.kernel.org>,
	<netdev@vger.kernel.org>, <linux-mm@kvack.org>
Subject: Re: [PATCH -next 2/4] tun: Make use of str_disabled_enabled helper
Date: Tue, 3 Sep 2024 14:25:53 +0800	[thread overview]
Message-ID: <9d844c72-bda6-4e28-b48c-63c4f8855ae7@huawei.com> (raw)
In-Reply-To: <66d5cc19d34c6_613882942a@willemb.c.googlers.com.notmuch>



On 2024/9/2 22:30, Willem de Bruijn wrote:
> Andy Shevchenko wrote:
>> On Sat, Aug 31, 2024 at 01:07:41PM -0700, Jakub Kicinski wrote:
>>> On Sat, 31 Aug 2024 17:58:38 +0800 Hongbo Li wrote:
>>>> Use str_disabled_enabled() helper instead of open
>>>> coding the same.
>>
>> ...
>>
>>>>   		netif_info(tun, drv, tun->dev, "ignored: set checksum %s\n",
>>>> -			   arg ? "disabled" : "enabled");
>>>> +			   str_disabled_enabled(arg));
>>>
>>> You don't explain the 'why'. How is this an improvement?
>>> nack on this and 2 similar networking changes you sent
>>
>> Side opinion: This makes the messages more unified and not prone to typos
>> and/or grammatical mistakes. Unification allows to shrink binary due to
>> linker efforts on string literals deduplication.
> 
> This adds a layer of indirection.
> 
> The original code is immediately obvious. When I see the new code I
> have to take a detour through cscope to figure out what it does.
If they have used it once, there is no need for more jumps, because it's 
relatively simple.

Using a dedicated function seems very elegant and unified, especially 
for some string printing situations, such as disable/enable. Even in 
today's kernel tree, there are several different formats that appear: 
'enable/disable', 'enabled/disabled', 'en/dis'.

Thanks,
Hongbo

> 
> To me, in this case, the benefit is too marginal to justify that.


  reply	other threads:[~2024-09-03  6:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-31  9:58 [PATCH -next 0/4] Introduce several opposite string choice helpers Hongbo Li
2024-08-31  9:58 ` [PATCH -next 1/4] lib/string_choices: " Hongbo Li
2024-08-31  9:58 ` [PATCH -next 2/4] tun: Make use of str_disabled_enabled helper Hongbo Li
2024-08-31 20:07   ` Jakub Kicinski
2024-09-02  1:27     ` Hongbo Li
2024-09-02  6:10     ` Gal Pressman
2024-09-02 16:11       ` Jakub Kicinski
2024-09-02 10:49     ` Andy Shevchenko
2024-09-02 14:30       ` Willem de Bruijn
2024-09-03  6:25         ` Hongbo Li [this message]
2024-09-03 15:09           ` Andy Shevchenko
2024-09-04  2:27             ` Hongbo Li
2024-09-04 14:33               ` Jakub Kicinski
2024-08-31  9:58 ` [PATCH -next 3/4] mm: page_alloc: Make use of str_off_on helper Hongbo Li
2024-08-31  9:58 ` [PATCH net-next 4/4] net: sock: Make use of str_no_yes() helper Hongbo Li

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9d844c72-bda6-4e28-b48c-63c4f8855ae7@huawei.com \
    --to=lihongbo22@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=andy@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jasowang@redhat.com \
    --cc=kees@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=willemdebruijn.kernel@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox