All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dimitri Sivanich <sivanich@hpe.com>
To: Colin Ian King <colin.i.king@gmail.com>
Cc: Dimitri Sivanich <dimitri.sivanich@hpe.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] misc: sgi-gru: Fix spelling mistake "unexpect" -> "unexpected"
Date: Wed, 16 Mar 2022 07:12:44 -0500	[thread overview]
Message-ID: <20220316121244.GA30540@hpe.com> (raw)
In-Reply-To: <20220315222253.2960047-1-colin.i.king@gmail.com>

Acked-by: Dimitri Sivanich <sivanich@hpe.com>

On Tue, Mar 15, 2022 at 10:22:53PM +0000, Colin Ian King wrote:
> There is a spelling mistake in an error message. Fix it.
> 
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
>  drivers/misc/sgi-gru/grukservices.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/misc/sgi-gru/grukservices.c b/drivers/misc/sgi-gru/grukservices.c
> index 0ea923fe6371..19dbdad8ad8a 100644
> --- a/drivers/misc/sgi-gru/grukservices.c
> +++ b/drivers/misc/sgi-gru/grukservices.c
> @@ -1016,7 +1016,7 @@ static int quicktest1(unsigned long arg)
>  			break;
>  	}
>  	if (ret != MQE_QUEUE_FULL || i != 4) {
> -		printk(KERN_DEBUG "GRU:%d quicktest1: unexpect status %d, i %d\n",
> +		printk(KERN_DEBUG "GRU:%d quicktest1: unexpected status %d, i %d\n",
>  		       smp_processor_id(), ret, i);
>  		goto done;
>  	}
> -- 
> 2.35.1

      reply	other threads:[~2022-03-16 12:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-15 22:22 [PATCH] misc: sgi-gru: Fix spelling mistake "unexpect" -> "unexpected" Colin Ian King
2022-03-16 12:12 ` Dimitri Sivanich [this message]

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=20220316121244.GA30540@hpe.com \
    --to=sivanich@hpe.com \
    --cc=arnd@arndb.de \
    --cc=colin.i.king@gmail.com \
    --cc=dimitri.sivanich@hpe.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@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 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.