linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eli Billauer <eli.billauer@gmail.com>
To: Colin King <colin.king@canonical.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] char: xillybus: Fix spelling mistake "overflew" -> "overflowed"
Date: Tue, 01 Jun 2021 19:33:35 +0300	[thread overview]
Message-ID: <60B6615F.1050807@gmail.com> (raw)
In-Reply-To: <20210601102201.8489-1-colin.king@canonical.com>

On 01/06/21 13:22, Colin King wrote:
> There is a spelling mistake in a dev_err message. Fix it.
>
>    
This is actually a grammar mistake: Overflew is the past of overfly, not 
overflow.

I stand corrected nevertheless. Thanks.

    Eli

Acked-by: Eli Billauer <eli.billauer@gmail.com>

      reply	other threads:[~2021-06-01 16:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01 10:22 [PATCH][next] char: xillybus: Fix spelling mistake "overflew" -> "overflowed" Colin King
2021-06-01 16:33 ` Eli Billauer [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=60B6615F.1050807@gmail.com \
    --to=eli.billauer@gmail.com \
    --cc=arnd@arndb.de \
    --cc=colin.king@canonical.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).