Netdev List
 help / color / mirror / Atom feed
From: Alexandra Winter <wintera@linux.ibm.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [net] dibs: Improve DIBS prompts and help texts
Date: Wed, 13 May 2026 16:20:03 +0200	[thread overview]
Message-ID: <fd5245fa-b46c-4f83-955a-dc0376610b89@linux.ibm.com> (raw)
In-Reply-To: <1afbbbc74669f053414dcbabd909e52e7eae66e0.1778678915.git.geert+renesas@glider.be>



On 13.05.26 15:29, Geert Uytterhoeven wrote:
> The Kconfig prompts for the DIBS options read:
> 
>     DIBS support (DIBS) [N/m/y/?]
>       intra-OS shortcut with dibs loopback (DIBS_LO) [N/y/?]
> 
> Clarify the DIBS prompt by expanding the acronym.

Thank you, yes that is an improvement.


> Capitalize the first character of the DIBS_LO prompt, and always write
> DIBS in full caps.

dibs is a shim layer between other kernel components and code pieces are
typically lowercase, same for sysfs paths. It is not some formal standard
that is documented anywhere in uppercase. So I'd like to keep it lowercase
in the help text.

> While at it, join the first two lines of the DIBS help text into a real
> sentence.
> 
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
>  drivers/dibs/Kconfig | 18 +++++++++---------
>  1 file changed, 9 insertions(+), 9 deletions(-)
> 
> diff --git a/drivers/dibs/Kconfig b/drivers/dibs/Kconfig
> index 5dc347b9b2350667..f2dd4c3e7c5f6d72 100644
> --- a/drivers/dibs/Kconfig
> +++ b/drivers/dibs/Kconfig
> @@ -1,23 +1,23 @@
>  # SPDX-License-Identifier: GPL-2.0
>  config DIBS
> -	tristate "DIBS support"
> +	tristate "Direct Internal Buffer Sharing support"
>  	default n
>  	help
> -	  Direct Internal Buffer Sharing (DIBS)
> -	  A communication method that uses common physical (internal) memory
> -	  for synchronous direct access into a remote buffer.
> +	  Direct Internal Buffer Sharing (DIBS) is a communication method that

I could consider changing this to (dibs), if people think that is easier to read.
But I thought it more obvious this way.

> +	  uses common physical (internal) memory for synchronous direct access
> +	  into a remote buffer.
>  
>  	  Select this option to provide the abstraction layer between
> -	  dibs devices and dibs clients like the SMC protocol.
> -	  The module name is dibs.
> +	  DIBS devices and DIBS clients like the SMC protocol.
> +	  The module name is DIBS.

The module name is definitively dibs in lowercase.


>  
>  config DIBS_LO
> -	bool "intra-OS shortcut with dibs loopback"
> +	bool "Intra-OS shortcut with DIBS loopback"
>  	depends on DIBS
>  	default n
>  	help
> -	  DIBS_LO enables the creation of an software-emulated dibs device
> +	  DIBS_LO enables the creation of an software-emulated DIBS device
>  	  named lo which can be used for transferring data when communication
>  	  occurs within the same OS. This helps in convenient testing of
> -	  dibs clients, since dibs loopback is independent of architecture or
> +	  DIBS clients, since DIBS loopback is independent of architecture or
>  	  hardware.


  reply	other threads:[~2026-05-13 14:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-13 13:29 [PATCH] [net] dibs: Improve DIBS prompts and help texts Geert Uytterhoeven
2026-05-13 14:20 ` Alexandra Winter [this message]
2026-05-13 15:35   ` Geert Uytterhoeven

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=fd5245fa-b46c-4f83-955a-dc0376610b89@linux.ibm.com \
    --to=wintera@linux.ibm.com \
    --cc=geert+renesas@glider.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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