From: Colin Ian King <colin.king@canonical.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Inaky Perez-Gonzalez <inaky.perez-gonzalez@intel.com>,
linux-wimax@intel.com, "David S . Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] wimax/i2400m: fix spelling mistake "unitialized" -> "uninitialized"
Date: Mon, 24 Sep 2018 18:35:29 +0100 [thread overview]
Message-ID: <8889cb0c-9f21-0e4f-7938-658c87aad37e@canonical.com> (raw)
In-Reply-To: <db8575a7-a4ab-3234-3e59-06cdeffe0f59@cogentembedded.com>
On 24/09/18 18:27, Sergei Shtylyov wrote:
> On 09/24/2018 08:18 PM, Colin King wrote:
>
>> From: Colin Ian King <colin.king@canonical.com>
>>
>> Trivial fix to spelling mistake in ms_to_errno array of error messages
>>
>> Signed-off-by: Colin Ian King <colin.king@canonical.com>
>> ---
>> drivers/net/wimax/i2400m/control.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/net/wimax/i2400m/control.c b/drivers/net/wimax/i2400m/control.c
>> index 094cea775d0c..0475ad553707 100644
>> --- a/drivers/net/wimax/i2400m/control.c
>> +++ b/drivers/net/wimax/i2400m/control.c
>> @@ -257,7 +257,7 @@ static const struct
>> [I2400M_MS_ACCESSIBILITY_ERROR] = { "accesibility error", -EIO },
>> [I2400M_MS_BUSY] = { "busy", -EBUSY },
>> [I2400M_MS_CORRUPTED_TLV] = { "corrupted TLV", -EILSEQ },
>> - [I2400M_MS_UNINITIALIZED] = { "not unitialized", -EILSEQ },
>> + [I2400M_MS_UNINITIALIZED] = { "not uninitialized", -EILSEQ },
>
> I suspect they rather meant "not initialized".
Of course, that makes far more sense. I send a V2.
>
> [...]
>
> MBR, Sergei
>
prev parent reply other threads:[~2018-09-24 17:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 17:18 [PATCH] wimax/i2400m: fix spelling mistake "unitialized" -> "uninitialized" Colin King
2018-09-24 17:27 ` Sergei Shtylyov
2018-09-24 17:35 ` Colin Ian King [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=8889cb0c-9f21-0e4f-7938-658c87aad37e@canonical.com \
--to=colin.king@canonical.com \
--cc=davem@davemloft.net \
--cc=inaky.perez-gonzalez@intel.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wimax@intel.com \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.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;
as well as URLs for NNTP newsgroup(s).