All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Andrew Kreimer <algonell@gmail.com>
Cc: Dave Penkler <dpenkler@gmail.com>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] staging: gpib: Fix typo in TTY_LOG message
Date: Mon, 10 Feb 2025 13:32:22 +0100	[thread overview]
Message-ID: <2025021006-dominion-straining-bcb6@gregkh> (raw)
In-Reply-To: <20250210121552.33455-1-algonell@gmail.com>

On Mon, Feb 10, 2025 at 02:15:33PM +0200, Andrew Kreimer wrote:
> There is a typo in TTY_LOG message:
>  - sucesfully -> successfully
> 
> Fix it via codespell.
> 
> Signed-off-by: Andrew Kreimer <algonell@gmail.com>
> ---
>  drivers/staging/gpib/lpvo_usb_gpib/lpvo_usb_gpib.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/staging/gpib/lpvo_usb_gpib/lpvo_usb_gpib.c b/drivers/staging/gpib/lpvo_usb_gpib/lpvo_usb_gpib.c
> index 85322af62c23..1c3e5dfcc9ec 100644
> --- a/drivers/staging/gpib/lpvo_usb_gpib/lpvo_usb_gpib.c
> +++ b/drivers/staging/gpib/lpvo_usb_gpib/lpvo_usb_gpib.c
> @@ -542,7 +542,7 @@ static int usb_gpib_attach(gpib_board_t *board, const gpib_board_config_t *confi
>  		return -EIO;
>  
>  	SHOW_STATUS(board);
> -	TTY_LOG("Module '%s' has been sucesfully configured\n", NAME);
> +	TTY_LOG("Module '%s' has been successfully configured\n", NAME);

When drivers are successful, they should be quiet, this line should just
be removed.

thanks,

greg k-h

  reply	other threads:[~2025-02-10 12:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-10 12:15 [PATCH] staging: gpib: Fix typo in TTY_LOG message Andrew Kreimer
2025-02-10 12:32 ` Greg KH [this message]
2025-02-11  9:30 ` [PATCH v2] staging: gpib: Remove unnecessary TTY_LOG expansion Andrew Kreimer
2025-02-11 10:09   ` Greg KH
2025-02-11 11:28     ` Andrew Kreimer

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=2025021006-dominion-straining-bcb6@gregkh \
    --to=greg@kroah.com \
    --cc=algonell@gmail.com \
    --cc=dpenkler@gmail.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.